Ad spend mapping
Use Adjust's Ad spend mapping tool to configure app mapping rules to handle your web-to-mobile or web-to-web campaigns. You can also set up mapping rules for networks running mobile campaigns that don't provide App ID and Store type of the app.
Why do you need this solution?
Adjust needs the App ID and Store type of the app to match ad spend data to an app in AppView on your account. For some campaigns, the network's Reporting API doesn't provide these details:
- Web-to-mobile campaigns
- Web-to-web campaigns
- Mobile campaigns with certain partners (see list here)
With the Ad spend mapping tool, you can assign a campaign to an app in AppView. This ensures that ad spend data is available in your reports through Datascape or the Report Service API.
Example: If a network reports 100 installs and $50 ad spend from a campaign, Adjust can't tell whether the ad spend resulted in installs on iOS or Android. If you create a rule to assign ad spend to the iOS app, then $ 50 is reported under the iOS platform and App Store store type.
Before you begin
Here's what you need to know before getting started.
Requirements
- You need to be on the SpendWorks Base, Core, Enterprise or Custom package to access the Ad spend mapping tool. The available store type for rule creation depends on your SpendWorks package:
- SpendWorks Base, Core, Enterprise or Custom package - Google Play, App Store
- SpendWorks Enterprise or Custom package - Google Play, App Store, Web
- You retrieve ad spend data through the API integration solution.
- You need to have Admin or Editor permissions in Adjust.
- You need to have an app with an App ID in AppView.
Availability for SpendWorks Base, Core, Enterprise or Custom package
For networks running mobile campaigns that don't provide App ID and Store type of the app, you can create mapping rules. Here is a list of some of the networks running mobile campaigns for which app mapping rules will be processed. This list is not exhaustive.
- AdAction
- Fluent
- Pinsight Media
- Prodege
- RTB House - The RTB House reporting API doesn’t provide app information by default. You can request RTB House to configure your customer account to receive app information. If you still don't receive app information from RTB House, you need to create a rule.
- VK Ads (ex. MyTarget) - Create a rule only if you don't see ad spend data in your reports.
- Yandex Direct - Create a rule only if you don't see ad spend data in your reports.
Limited availability for SpendWorks Base package
If you're on the SpendWorks Base package, you can create mapping rules for certain partners, but they won't be processed. This is because these partners are commonly used for web campaigns, and web campaigns are available for SpendWorks Core and later packages only. Adjust won't process mapping rules for the following partners for the SpendWorks Base package:
- Google Ads
- Snapchat
- TikTok
Create a mapping rule
- You can create a rule for a single app and store type at a time.
- You cannot create multiple rules for the same campaign with different store types.
Follow these steps to create a mapping rule:
- Under DataWorks, select Ad spend mapping.
- Select Create mapping rule.
- Under Rule settings, turn the Status toggle to ON. This ensures that the mapping rule applies each time that ad spend data is being collected via the API integration or CSV upload.
- Select the partner for which you want to create the rule.
- In the Campaign identifier list, choose whether you want to search for campaigns by:
- Campaign name - Search for one or multiple campaigns.
- Campaign ID - Search for a campaign by ID.
- In the Condition list, select the condition that you want to apply to campaigns:
- Campaign is - Checks for an exact match with the specified value.
- Campaign contains - Checks campaign names and IDs that contain your input. This lets you map multiple campaigns to one app.
- In the Value field, provide an appropriate value based on the condition selected. If you had selected the Campaign contains condition, specify this value as a regular expression in the correct format.
- Under Select your app, select the app that you want to map the campaign to.
- (Multi-platform apps only) select the store type. The store type displayed depends on your SpendWorks package:
- SpendWorks Base, Core, Enterprise or Custom package - Google Play, App Store
- SpendWorks Enterprise or Custom package - Google Play, App Store, Web
- Select Create rule.
After you create and enable a rule, ad spend data for apps that match the pattern in the rule is pulled according to the daily automatic data collection schedule. You need to wait until the next data collection occurrence to verify if the rule that you've created is working properly and for the data to be available in Datascape reports.
Campaign value formatting
When you choose the Campaign contains condition while creating a rule, you need to specify the value as a regular expression.
If campaign name contains +, you need to add \ before + for the rule to work correctly.
You can use the following rules of characters and regular expressions:
| Anchors | |
^Campaign | Matches any string that starts with Campaign. |
Campaign$ | Matches a string that ends with Campaign. |
^The Campaign$ | Exact string match - starts and ends with Campaign. |
| Case sensitivity | |
campaign | Matches case sensitivity of the string campaign. |
(?i)campaign | Doesn't match case sensitivity of the string campaign. |
[Aa][Bb][Cc] | Matches the letters "abc" in any combination of uppercase or lowercase (e.g., "abc", "Abc", "aBC"). |
| Character classes | |
\d | Matches a single character that is a digit. |
\w | Matches a word character (alphanumeric character plus underscore). |
\s | Matches a whitespace character (includes tabs and line breaks). |
\d{3,5} | Matches a digit with a length between 3 and 5. |
| Quantifiers | |
campaign. | Matches a string that has campaign followed by any character. |
campaign* | Matches a string that has campaign followed by zero or more n. |
campaign+ | Matches a string that has campaign followed by one or more n. |
campaign? | Matches a string that has campaign followed by zero or one n. |
campaign{2} | Matches a string that has campaign followed by 2 n. |
campaign{2,} | Matches a string that has campaign followed by 2 or more n. |
campaign{2,5} | Matches a string that has campaign followed by 2 up to 5 n. |
c(ampaign)* | Matches a string that has c followed by zero or more copies of the sequence ampaign. |
c(ampaign){2,5} | Matches a string that has c followed by two up to five copies of the sequence ampaign. |
campaign.* | Matches a string that has anything after campaign. |
.*campaign.* | Matches a string that has anything before and after campaign. |
Manage mapping rules
The Ad spend mapping tool is available under DataWorks > Ad spend mapping. The tool gives you an overview of the following:
- ID - The identifier of the rule. Always share the rule ID with your Technical Account Manager if you have questions or need to discuss issues.
- Created - The date and time when the rule was created.
- Partner - The name of the advertising network for which the rule has been applied.
- Campaign identifier - The Campaign ID or Campaign name you want to use to search for campaigns.
- Store type - The store type of the app for which the rule applies.
- App - The app for which the rule is applied. You can only select one app with a given rule.
- Status
- Enabled - The mapping rule applies each time ad spend data is collected through the API integration solution.
- Disabled - The mapping rule doesn't apply and even if a campaign matches that rule, it isn't associated with the app.
- Actions
- Edit - Edit an existing rule mapping. You can enable or disable the rule and/ or modify the partner, campaign identifier and its value, and app.
- Delete - Delete a rule.
Edit a rule
You need to edit a rule in the following cases:
No app associated with the App ID specified in the rule
Under App, you will see None. Hover over this to see the value of the App ID of the app that was initially associated with the rule. This happens if you have modified the App ID of the app, or have deleted the app in AppView. In this case, your rule doesn't work until you select a new app and assign it to the rule.
Multiple matching apps in the current rule
Under App, you will see a count of the number of apps that match the selected app ID and store type. Hover over this to see the names of apps. In this case, your rule works but the campaign data is associated only with the first app ordered alphabetically by its app token in your reports.