Let's begin with creating a basic banner ad.
Step 1 - Details Section
The details screen contains the following fields:
Campaign: You can select from a drop down list of all active campaigns and select a campaign to assign this content into. The campaigns are created separately from the campaigns screen at a merchant level.
Placement: Placement for content is a preconfigured list of places where the content can be displayed - for example: Carousel, Top Banner, Full Screen.
Title: A text based title for the content. May or may not be shown in the app - defined by the app. 30 character max.
Description: A text based description for the content. May or may not be showing in the app - defined by the app. 3000 character max.
Start And End Date and Time: The start and end date and time for the content.
Event Start Date and Time: A secondary field to record the start date of an event associated with the content. The app may use this field in a number of ways.
Days of the Week: Select which days of the week the banner ad will be available to consumers.
Click URL: If the content is clicked on the consumer can be taken to an external URL. (Optional field).
Content URL: If the content requires an image that is hosted in a third party location a URL can be used. (Optional field).
Extended Data: Extended data is a flexible option that allows additional data to be added to the content that doesn't fit into another existing field. Extended data can be structured code, comma separated values, web URL's or plain text. Different applications may make use of this field dictated by their own business needs.
No Compete Group: When multiple items of content are in the same no-compete group only the one with the highest weighting will be visible to the consumer. This is useful when there are several pieces of content for an identical product targeted at slightly different audiences, this means if there are any overlaps in the target audiences only the piece of content with the high weighting will be shown. (Optional field).
Step 2 - Images Section
Content can be given an image and/or one or more digital assets.
The image cropping tool is pre-configured to a set resolution (decided during early consultation with the client and configured by Plexure technical support shortly after platform deployment). We recommend selecting an image ratio that will work across all screen sizes and then uploading all images at the maximum size they will ever be required. The apps using this image can request the image in any scaled size at or below the original. For example if the high resolution original image uploaded is 1000 x 600, an app could request the same image at 500 x 300, or 250 x 150 if it has a smaller screen.
The assets section can support the uploading of multiple additional digital assets. Supported file types are: pdf, jpg, png, jpeg, mp4, mp3, mov, gif, csv, son, xml, xls, xlsx, doc, docx, txt.
Step 3 - Channels Section
The channel defines where the content ends up. Plexure can support multiple pre-configured channels. The most common channel used by clients is the mobile app channel - selecting this means the content will appear in your mobile app.
Step 4 - Filter Section
The filter and weighting area for content supports a number of options. Firstly there are filters like consumer tags, operating conditions and content tags which allow you to turn the banner ad on and off for different groups of consumers. These filters are binary, and are used to restrict (target) who sees the content. A more detailed description of each of these is below:
Consumer Tags: Consumer tags are data points assigned to a consumer's profile, by selecting one or more consumer tags as filters it means that only consumers who have the selected tag(s) will be able to access the banner ad. Consumers without the selected tag(s) will not see the banner ad at all. Consumer tags are setup separately from banner ad creation and there are a number of ways a consumer ends up with a given tag.
Operating Condition Tags: Operating conditions are a group of tags that are enabled or disabled at a platform level. They can be either platform wide or regional and they can be manually updated or automatically updated. The most common use is automated weather operating conditions, so you might select the weather conditions relevant to the banner ad. This means that only consumers in a region with the selected weather operating condition(s) active will be able to see the banner ad. Consumers in a region with the operating condition disabled will not see the banner ad.
Content Tags: Content tags are tags that describe the content in some way, for example an banner ad for beer might have the "Nightlife" content tag, or the "Male" content tag. The app could then filter various pieces of content based on their content tags choosing to display that given banner ad only to people who have indicated a preference for Nightlife content.
Weighting: Weighting is a numeric number assigned to the banner ad, it can be both positive or negative and can be up to five digits long. Apps may choose to order content by weighting - for example: From highest weight to lowest weight. There are several types of weighting that combine to form a total weighting, the backend user can select none, one or a range of weighting options. Base weight is a one off numeric weight applied to the banner ad. Weight by consumer tag allows for additional weight to be added for consumers who have the specified tag - different tags can be assigned different weights, negative weighting can also be used here. Add weight by operating condition allows for additional weight to be added to be added to the banner ad in any region where the operating condition tag specified is active. Add weight by proximity adds weighting points based on how close a consumer is to a store involved with the banner ad.
Step 5 - Beacon Groups Section
Filtering by beacons means that only consumers who are in range of the selected beacons will be able to see the banner ad. Consumers outside the range of the beacon will not see the banner ad.
Step 6 - Location Section
Geo-fences and geo-fence groups are setup separately in merchant settings. From this section you can select to make the banner ad available everywhere (ie: No geo-fences will be used), or to restrict the banner ad to consumers only within a certain geo-fence or group of geo-fences. It's important to note that if geo-fences are used, consumers not inside the geo-fence will not see the content at all.
Step 7 - Stores Section
You can select from a list of stores or groupings of stores which are pre-setup in the merchant settings area. The stores are sent to the app along with the banner ad details and the app may choose to display a list of stores to which the banner ad is relevant.
Step 8 - Start Section
After completing the banner ad setup the banner ad can be saved as a draft and finished later or published immediately meaning it will be active based on the options selected.