Mobile Targeting Summary
CAKE has expanded its service offering to capture, track and report mobile client data. This includes demographic and technical information, such as country, language, carrier, OS, device, etc. Leveraging this data CAKE will provide the ability to target users by these demographic and technical details as well as track and report these data points.
Mobile Targeting is separated into two components, the targeting engine and reporting. This primer will cover the targeting engine component.
Mobile Targeting High Level Workflow
Mobile targeting introduces a powerful tool that allows users to route traffic to offers,based on a series of mobile rules. You can create your normal offer, create one or more mobile rules – ex. - an iPhone mobile rule which would identify iPhone traffic and redirect to an iPhone offer. Once enabled CAKE would scan inbound clicks and based on the defined rules, we would route users to that iPhone offer.
Mobile Rule Basics
With CAKE’s new mobile infrastructure you now have the flexibility to create mobile targeting rules that route in-bound clicks to a mobile branded user experience. These mobile targeting rules can be created at the offer level and are defined as a one-to-one relationship between the rule and offer/offer contract.
A mobile rule is a placeholder for one or more mobile targets and has a one-to-many relationship to mobile targets. Targets are the specific parameters used to route traffic and consist of the following types:
Rule Target Types
- User Agent Match
- Operating System
- Percentage Split
User Agent Targeting:\L User Agent is a text box that allows you to define specific HTTP header information to target against. This field expects valid regular expression data – example - @"^(?!opera)(?=.*\b(android|iphone|ipod)\b).*$"
Location:\L Similar to our geo based targeting you can select specific countries and/or regions (or states
as potential targets. This will allow CAKE to determine the inbound click’s geographical location and route users to an offer.
Device:\L CAKE has partnered with best of breed data providers and aggregated thousands of device patterns to help target based on mobile device. Through a user agent scan we can determine the specific device or manufacturer for targeting purposes.
Operating System:\L Similar to our device pattern matching CAKE leverages user agent patterns to help target based on operating system. Based on this pattern we can determine the specific operating system or range of operating system matches for targeting purposes.
Browser:\L Similar to our device pattern matching CAKE leverages user agent patterns to help target based on browser.
Language:\L Similar to our device pattern matching CAKE leverages user agent patterns to help target based on language.
ISP/Carrier:\L CAKE has partnered with best of breed data providers and implemented a large database of IPs and carriers to help determine the network the initial click traffic flowed through.
Percentage Split: \LYou can assign a percentage value (0-100), which would split traffic between rules based on those percentages. It follows the same hierarchical logic that our rules already follow (first rule analyzed first, second rule analyzed, etc.). When you assign a percentage split value of 90 (90% on an initial Rule – all traffic that matches the rule has a 90% chance of routing to the offer associated. 10% of that remaining traffic would move on to the next Rule.
Mobile Targeting Examples
Now that we’re familiar with the mobile rules and targets let’s look at some examples of how you can leverage these on an offer.
Mobile targeting expands on our existing geo targeting rules, but works as a separate function. New offers and existing offers can leverage mobile targeting, but since they are separate functions you must choose one type per offer. If you already have a number of existing offers that leverage geo targeting you can keep those unchanged and only leverage mobile targeting on all new offers. Or you can take an existing offer and switch the geo targeting to mobile targeting and leverage the geo capabilities within mobile targeting.
Mobile Interface Walk-Thru
• Open an Offer card
• Select the “Traffic” tab
• Each rule can be redirected to an offer or offer contract.
• Within each rule you can define multiple rule targets which are made up of the various mobile parameters we reviewed in an earlier section. In the above example, we have a rule called “iPhone Traffic”. When you select the “Edit” icon for that rule it will open up the rule targets window (below). In this particular example, we have defined a rule target that matches on an iPhone mobile device. Under this rule when we determine a click originated on an iPhone we would route this click to the redirect (Offer Contract called “CAKE Mobile Install - iPhone - CPA - Public").
• Rules are hierarchical in nature – in other words, the listed order of your rules will determine the order in which they are executed. In the above example, the rule “iPhone Traffic” would be scanned first, "iPad Traffic" second, “Android Traffic” third and so on. Once a rule has been matched the click is immediately routed on the fly and no further rules will be read. Once you’ve created a rule, it’s easy to change the rule targets, hierarchy, etc.
New Mobile Offer Rules
• In the example below, we will define a rule target for operating system.
• Within CAKE, open up an Offer card.
• Select the “Allowed Traffic” tab.
• Select “Rules” and hit “Apply.” This will enable mobile targeting on this particular offer.
• Now that mobile targeting has been set you can select “Edit” which will load the initial window to create mobile rules.
• Since this is a newly defined mobile offer, the mobile rules screen should be blank.
• Click on “New Rule”. This will open a new window to allow you to enter in a name for the rule and the redirect destination.
\L • Also, in this window are “Active” and “Shared” checkboxes. Active defines whether or not the rule is enabled. Shared defines whether or not this rule can be accessed on other offers. At times, it can be more efficient to define a general rule and then utilize it across multiple offers without having to recreate the rule each time.
\L • Select a name for the rule ("Android Match", for example and then select a redirect target – offer or offer contract. The red highlight indicates that these are mandatory fields. For name, use a descriptor that would best describe the rule being created (“Operating System Match Rule – iOS 5”, for example).
• From the “Add Rule Target” drop down box, select a Target Type – in this case, operating system. CAKE gives you a number of data points to match on – OS type (iOS), OS Major Version (iOS 5 or OS Minor Version (iOS 5.0.1). You also have the flexibility to add a range or target a specific OS type – you can target a range of OS types or OS major versions (iOS 5 to iOS 6), or a specific major or minor version.
• Please note that each rule target type has a “Not Match” checkbox. When this is checked the criteria selected will be excluded by the rules engine. For example, you could select to target all mobile carriers except “AT&T”. All you’d have to do is add the AT&T group as a target and then check the “Not Match” checkbox. When the rule is parsed the inbound clicks will be redirected from all carriers except AT&T.
• If you need to change the target types within a rule, simply click the “Edit” icon on the rule line (to the right). This will open up the target types and you can select the “Edit” icon (that looks like a paper with a pencil over it on the Target line to edit those.
Editing the Rule: