Sidan du har begärt finns tyvärr inte på ditt språk för närvarande. Du kan välja ett annat språk längst ned på sidan eller översätta vilken webbsida du vill till valfritt språk direkt med hjälp av den inbyggda översättningsfunktionen i Google Chrome.

Custom Floodlight variables

Custom Floodlight variables enable you to capture information beyond the basics (visits and revenue) that you can collect with standard parameters in your tags.

Custom variables use the (case sensitive) keys u1, u2, and so on, and can take any values that you choose to pass to them. You can include custom Floodlight variables in any of your Floodlight activity tags and report on their values in Report Builder. You can create up to 100 custom variables per Floodlight configuration. You can also add friendly names to make these parameters easier to understand in reports.

You can also use custom variables to build audience lists in Campaign Manager 360 and Display & Video 360

Example use cases

There are lots of creative ways that you can use custom variables:

  • Location: Pass the area code, the shipping or billing postal code, the region, etc.

  • Travel and vacation: Pass the number of nights booked for hotels, participation in a rewards program, route or fare details for travel, etc.

  • Products: Pass the product name, product description, shipping amount, etc.

  • Loyalty: Pass an indicator that shows whether the user is a new or a returning customer.

There is no character limit for custom variables, but remember that the length of your variables adds to the total length of the URL in the user's browser. This is important because total URL length is limited in some browsers.

Create custom variables

To create or edit a custom variable:

  1. Find the advertiser you want to work with and go to Floodlight > Configuration, then click Custom Floodlight variables.

  2. For each custom variable you want to create or edit, enter a Friendly Name, which is the name for the variable that is used in reports. For example, if you are using a custom variable to include users' ZIP codes in the Floodlight tags, you could use ZIP Code as the Friendly Name.

  3. Choose the Type of custom variable you're creating. Choose string if you want the variable to include alphanumeric characters or special characters. Choose number if you want to pass numeric values. There are a few considerations for variable values:

    • There is no character limit for custom variables, but remember that the length of your variables adds to the total length of the URL in the user's browser. This is important because total URL length is limited in some browsers.
    • String variables do not accept the following characters: ", < , > or #.
    • Number variables use a decimal point (.) as a separator, such as 3.5.
    • Special characters need to be URL encoded to avoid processing issues.
  4. Click Save.

Please take care when using parameters in tags. The terms of your Google Marketing Platform contract prohibit passing any information to us that we could use or recognize as personally identifiable information (PII). If you enter certain values into a field in a Google Marketing Platform product, you may see a warning that reminds you that you must not use parameters to pass data that we would recognize as PII. Parameter friendly names that trigger this warning include, for example, email and username. Note that it is okay to use these friendly names if your purpose is not to collect information that Google Marketing Platform could use or recognize as PII. (For example, a custom variable with the friendly name email and the value weekly is fine, but passing a user’s email address is not.) If we see any cause for concern, we may contact you to confirm that you are not using parameters in a way that is prohibited.

 

Learn more about our best practices to avoid sending PII.

Was this helpful?

How can we improve it?

Need more help?

Try these next steps:

Search
Clear search
Close search
Main menu
10179477454217153310
true
Search Help Center
true
true
true
true
true
69192
false
false