Follow these steps to create a new Floodlight activity for every event you want to track. You also have the option to create and edit floodlight activities using a bulk sheet.

1. From an advertiser, click Floodlight > Activities.

2. Click New and Name your Floodlight activity.

3. (Optional) Select Play install tracking if you're using the Floodlight activity to track app installs from Google Play.

4. Enter the URL where you plan to add the tag in the Expected URL. This can help you identify where the tag for your Floodlight activity has been placed.

5. Choose a Type, either counter or sales. Learn more.

6. Assign the activity to an Activity group or create a new one. Keep in mind that Campaign Manager 360 only shows activity groups for the type you've selected for the activity.

7. Pick a Counting method for conversions. The options available depend on whether you're creating a counter or sales activity.

Counter activities:
Standard: Counts every conversion
Unique: Counts the first conversion for each unique user during each 24-hour day.
Per session: Counts one conversion per user per session. You can define the length of a session for your site.

Sales activities:
Transactions: Counts all conversions, plus the total number of sales that take place and the total associated revenue.
❏ Items sold: Counts each conversion, plus the total number of items sold and the total associated revenue.

8. Select a Tag format from the options described above. For Google Tag Manager users, this setting determines what underlying tag format will be sent to your container when pushing activities to Google Tag Manager. If you choose iframe or global site tag, Tag Manager will use an iframe tag. If you choose image, Tag Manager will use image tags.

9. Click the checkbox next to Enable for attribution to enable attribution on the Floodlight activity. This is enabled by default for new activities. All attribution will stop for the activity if you do not enable this.

10. (Optional) If you're using Google Tag Manager to manage your Floodlight activities, follow the instructions to push tags to your container. Learn more.

11. (Optional) Set any Advanced properties you want to add:

a) Require SSL-compliant tags: This setting makes it required for Floodlight tags to be implemented on a secure site and that your tag doesn't call non-secure content. It is required by default. That means you won't be able to add code that calls any URL beginning with http. Learn about SSL compliance or how to resolve Floodlight compliance issues.

b) Activity tag string: Add a custom key-value that identifies the Floodlight activity, or leave this field blank to use a default value based on the activity name. This value cannot be changed after saving your activity.

c) For iframe and image tags only:

i. Generate XHTML-compliant tags: Select this option if your website requires XHTML validation.

ii. Use cache busting: This option inserts a random string into each image request URL to prevent browsers from retrieving a cached version. This ensures that each visit to a tagged page generates a new impression.

12. Include any Custom Floodlight variables you've created and would like to use for this activity. Learn more

13. Save your activity.

Once you've saved your Floodlight activity, click the Floodlight tag preview section to see a preview for the tag. Do not use the preview that's available before you save the tag; this is just a sample of the tag. All of the fields for your tag will be populated after you save.