Within ONE by AOL: Mobile Self Serve, users can optimize a campaign by using Site Optimization. Site blocking or targeting enables users to select to "Never Run On Certain Sites" or "Only Run On Certain Sites". This option is available in the Optimization & Targeting section of campaign setup.
Note: Users may collect Site IDs from their data or view eCPA in the Site Activity box in order to gauge performance and know which Site IDs to block or target.
- Select "Add Targeting" in the Site Optimization box. A modal will pop up.
- Find the Site Optimization Type drop-down menu and select either "Never Run on Certain Sites" or "Only Run on Certain Sites" depending on your campaign strategy.
- You have one of two options:
- Type in or copy and paste the Site IDs (APIDs) you wish to target or not target for this campaign. Enter one Site ID per line in the Bulk assignment field; OR
- View campaign data from the Site Activity chart to analyze impressions and CTR of the campaign. If you have ONE by AOL: Mobile Self Serve conversion tracking implemented, the eCPA column will also populate. The Site Activity table will populate data for Campaign Lifetime, Last 30 Days or Last 7 Days.
- Use the arrow button to add the Site IDs to the “Never Run On These Sites” or "Only Run On These Sites" column.
- Users can search the “Never Run On These Sites” or "Only Run On These Sites" column if a Site ID needs to be removed from the list once the Site ID is selected. Click on the trash can icon to remove that Site ID.
- Click the "Save Optimization" button to save your selections.
To activate a campaign for tracking Site IDs, follow the instructions for Basic Tracking below. If users prefer to use their own keys, implement site ID tracking using the Customized Tracking option.
Note: When optimizing, please keep in mind that blocking sites may decrease the pool of potential impressions and possibly decrease delivery of the campaign.
Users will need to append the parameter [:_mm_apid:] to the campaigns Destination URL, which sends the Site ID on the corresponding click. This parameter includes both the name and variable.
As seen in the example above, appending the parameter to the Destination URL will add a key value pair to the Destination URL so that the Site ID can tracked on the users side.
If a user prefers to use a defined key instead of displaying “mm_apid” in the Destination URL, Customized Tracking can be implemented.
Adding [:_jv_apid:] to the Destination URL allows users the ability to set a custom defined key to refer to the Site ID. In this case, users will define the name of the parameter and only the referring Site ID will be appended to your Destination URL.
- Advanced Usage: http://mmedia.com?custom_key=[:_jv_apid:]
- Resulting URL: http://mmedia.com?custom_key=357
As seen in the example above, using [:_jv_apid:] would provide just the value of the Site ID when the click occurs. For example, if an ad delivered to apid=357, the servers will only pass 357 with a custom variable of the users choosing.
If you have any questions, please contact us.