Digital Coupon Template

The Digital Coupon Template allows to predefine the configuration of coupons to be used on campaigns to help you create images and other user interface elements aligned with your brand. You will be able to customize the Coupon's appearance for both iOS and Android devices.


It consists of a single UI screen with an entry section to the left and a preview screen to its right that will render the Coupon contents as you define each element of the template.


Because the template addresses both iOS and Android based devices, some of its elements are device specific, so keep this in mind as you configure the template.

These are the steps.

  1. Enter the Issuer Name. The Issuer Name will
    • identify the Template in the main templates section,
    • appear in the lock screen notification and on the top of the Google Pay Pass.

  2. Enter the Coupon Title Program Name. The Coupon Title Program Name will
    • appear in the top of iOS backside and
    • appear as the Coupon title in Google Pay Pass

  3. Enter the applicable Offer Disclaimer. This is the fine print related to the coupon’s applicability.
    • It will appear in the back of the Coupon and
    • further down on the Android screen as you scroll in that direction

The image below identifies these three areas.


In Design is where you introduce the images related to your coupon, define the colors for the background, labels and their related values, and which Barcode to use, if any. Follow the detailed instructions and recommendations detailed for each element.


Header is an iOS Specific element of Coupon setup and it refers to the content that will appear in the top right corner of the iOS version of the coupon.


It has three variables that need to be defined.
• Type
• Label
• Value

The Type field can either be Generic or Unique.


A Generic type is one that has no expected value and can be whatever you choose, whereas a Unique type has values restricted to the platform defined Fields.

The Label field is what identifies an item in the Coupon.

The Value field is dependent on the Type selected for this entry. For the Generic Type case, the Value field can be used to establish a monetary amount or a discount percentage or something that describes the value proposition of the Coupon, but it has no restrictions as what can be entered.

For the Unique Type case, the Value field, as we mentioned above, will be restricted to the options offered by the pull-down menu displaying the existing platform fields, this is, the fields that are used throughout the platform to customize other types of campaigns and broadcasts. (See the example below).


This method of introducing data onto the Coupon template is used throughout the other sections.

Through the Main Fields you can offer the details of the Coupon promotion. It also addresses iOS and Google Pay Passes to best adapt to each coupon configuration. You have the option of configuring up to three Fields for the Coupon presentation to cover all the promotional information.


For the case of iOS, the Main Fields will be located immediately under the Strip Image, and for the Google Pay Pass, because of its configuration, the Main Fields can be found by scrolling down on the phone screen to uncover them.

Configuring the Main Fields is done the same way as it was done for the iOS Header, having the same elements, characteristics and constraints. The Type can be Generic and Unique, Label identifies the Coupon items, Value shares the same properties as the case of iOS Header. Below is an example of a fully defined Main Fields section.


Notice that once a coupon field is defined you have the option to edit it or delete under Actions.

Backside Fields addresses the “reverse side” of the Coupon. As shown in the template configuration screen, you can configure up to 5 fields.


Again, the configuration of each Field uses the same approach that was used for the other areas above: Type, Label, and Value, with the added twist of ensuring that the data format of the contents of the Generic Type Value be restricted to the format option you select in the Format entry box, whereas before, the Generic Type Value was open to have any value.


The data entered in the Value box must conform to the Format selected from the options shown. These are strictly formatting options and are not to be confused with Subscriber platform Fields. A fully populated Backside Fields section is shown below.


An iOS pass has an additional section that can be defined that involves relevant locations for the application of the iOS pass or Coupon. Define them by configuring the Locations section.


A pass can have up to ten relevant locations. Begin configuring them by selecting Add New Location. The following popup window will appear.


In it, you will be able to pin point the relevant location by either
• entering the complete address in the Address box. For example,
Lincoln Center Plaza, New York, NY 10023, United States
• by dragging the pin and searching in the map which can be expanded to full page view through the icon in the top right, or
• providing the coordinates, which requires to you to check the Advanced Location Settings box and enter the coordinates in WGS 84 Web Mercator coordinates. For example, Latitude: 40.7725 Longitude: -73.9835.

You can repeat this process until you have reached the 10 locations, if needed.

To end the template creation Select Save.

You will taken to the main Templates screen where the template will appear as the last entry in the Coupon Section of the Template matrix.

iBeacons is an Apple’s technology standard, that allows Mobile Apps to listen for beacon signals and react accordingly. It allows Mobile Apps to understand their position on a micro-local scale, and deliver content to users based on location using Bluetooth Low Energy technology.

At the very bottom of the of the Content FIelds section you can set up the iBeacons to be detected by your app. Up to 10 iBeacons can be include. For this you will need the UUID for the beacons you wish to detect and optionally, the Major and Minor values if you deemed them necessary, which is dependent on how the beacons are distributed in the area and how they are interrelated.


To start defining the iBeacons,

  • Select the UUID entry and enter the UUID value
  • If required enter the Major and Minor value in their corresponding boxes
  • Enter the text content in the corresponding box
  • Repeat this process for as many iBeacons you need for your campaign by selecting Add and entering the next corresponding UUIDs, Major, Minor, and Text parameters.

Enter the UUID(s) for as many beacons you intend to detect, up to ten, with the corresponding Major and Minor values to ensure successful iBeacon detections. Only the UUID and Text fields are strictly mandatory, while the Major and Minor values are available to afford more granularity in the iBeacon detection process given your beacon deployments.

The following figure shows a sample setup for two different beacon deployment strategies that address different beacon density scenarios. One addresses a metropolitan area deployment, on the top, and the other, an in store scenario.


The entries of the table can be edited or deleted by using the Action icons at the end of each table entry.