Apply custom settings

At various points in the template creation flow, settings allow you to define customizations for particular advertising platforms or client accounts.

For specific advertising platforms and client accounts, click Add a custom setting to configure any custom settings you require during template setup.

The potential scope of customization is broad. For example:

• You may need to include different regional customization requirements for different client accounts.
• You may want different names, different start and end dates to accommodate national holidays, or different location targets.
• You may have different tracking requirements.
• You may want to apply custom prefixes that reflect different advertising platforms in names.

Template custom settings example

Example Airways (www.example.com) is marketing a range of scheduled international flights and has a requirement to do this on a regional basis.

• There are two brands – one for inter-European flights, and the other for transatlantic USA-to-Europe flights. The inter-European product line is branded as "Golden Eagle Flights,” while transatlantic tickets are marketed as "Albatross Flights".
• Both brands each have two client accounts, one for Google Ads and another for Microsoft.
• A single set of templates manages flight promotions for both brands.
• The airline uses custom settings in the campaign template to set up separate branded campaigns targeting local holidays in the different regions, with different target audiences and budgets.

At Stage 2 "Campaign settings" in the campaign template, the following settings are applied:

1. In "Campaign name", the feed columns to be used in the custom setting must be entered as the primary setting:
   f:"brand" & f:"origin_country" & "f:destination_country"
2. Two custom settings for the campaign name are created:
   • In Albatross Flights client accounts:
     f:"brand" & " Thanksgiving breaks " & f:"origin_country" & “ to ” & "f:destination_country"
   • In Golden Eagle Flights client accounts:
     f:"brand" & " New Year breaks " & f:"origin_country" & “ to ” & "f:destination_country"
3. The two brands have different budgets, which are set using a custom setting for each pair of client accounts:
   • For Albatross Flights client accounts, a dynamic budget is created depending on ticket price: if(f:"price_usd" > 1000, 100, 50)
   • For Golden Eagle Flights client accounts, a static budget of 50 is entered.
4. In "Start and end dates", Albatross Flights campaigns are scheduled to run from May until October using a custom setting based on its client accounts. Another custom setting is used for Golden Eagle Flights client account campaigns running from May until December.
5. In "Locations", different target audiences are defined:
   • For Albatross Flights client account campaigns, the option for United States and Canada is selected.
   • For Golden Eagle UK Flights client account campaigns, a custom setting is entered for various European countries, including the United Kingdom, Ireland, and France.
6. In "Campaign URL options", the same base URL format is used in a custom setting for each advertising platform, but different user information is tracked using different parameters in the Final URL suffix. Note that {lpurl} substitutes the landing page URL for both in the tracking template. (The Final URL for the landing page can be set in the RSA template or the keyword template. If it's set in the keyword template, the keyword Final URL is applied. However, the Final URL is usually set in the RSA template.)

   • For Google Ads client accounts, the campaign, keyword, and device type are tracked. The Final URL suffix is "src=google"
     
     Final URL suffix:
     ?campaign=[*Campaign*]&keyword=[*KeywordID]&device={device}&o_country=" & f:"origin_country"&src=google

   • For Microsoft client accounts, only the campaign and keyword are tracked. The Final URL suffix is "src=msft"
     
     Final URL suffix:
     ?campaign=[*Campaign*]&keyword=[*KeywordID]&o_country=" & f:"origin_country"&src=msft