|
| 1 | +--- |
| 2 | +title: Google Tag for Campaign Manager |
| 3 | +strat: google |
| 4 | +hide-boilerplate: true |
| 5 | +hide-dossier: false |
| 6 | +id: 64f2434e5066280a0e7f1ab3 |
| 7 | +versions: |
| 8 | + - name: "Google Tag for Campaign Manager" |
| 9 | + link: '/docs/connections/destinations/catalog/actions-google-analytics-4/' |
| 10 | +--- |
| 11 | + |
| 12 | +{% include content/plan-grid.md name="actions" %} |
| 13 | + |
| 14 | +[Google Tag for Campaign Manager](https://support.google.com/analytics/answer/12325075){:target="_blank"} (formerly known as DoubleClick Floodlight) is Google's tool to measure ad impressions and report on conversions. With this integration, Segment customers can make use of their existing tracking implementation to send data to Campaign Manager 360 without having to manage additional tags or code on their site. |
| 15 | + |
| 16 | +When you have Segment installed and enable this destination, Segment takes care of loading the Google Tag (gtag.js library) for you, ensuring data is forwarded to your Floodlight configuration in Campaign Manager. |
| 17 | + |
| 18 | + |
| 19 | +### Getting Started |
| 20 | + |
| 21 | +1. Before you connect Segment to Google Tag for Campaign Manager, ensure you have set up your Floodlight configurations in Campaign Manager. |
| 22 | +2. Navigate to the Segment web app, select Catalog, then click on Destinations. |
| 23 | +3. Search for "Google Tag for Campaign Manager" in the Destinations Catalog and click on the destination. |
| 24 | +4. Choose "Configure Google Tag for Campaign Manager." |
| 25 | +5. Select the appropriate source that will forward data to Campaign Manager. |
| 26 | +6. On the Settings tab: |
| 27 | + * Enter the Advertiser ID found under Floodlight -> Configuration in Campaign Manager. |
| 28 | + * Set Allow Ad Personalization Signals as per your need. |
| 29 | + * Decide if you want to enable Conversion Linker which helps with first-party cookie tracking. |
| 30 | +7. Once done, Segment will begin forwarding the appropriate events and conversions to your Floodlight configurations. |
| 31 | + |
| 32 | +--- |
| 33 | + |
| 34 | +### 1. Sales Activity |
| 35 | + |
| 36 | +Capture monetary conversion data like revenue, order quantity, and transaction ID. |
| 37 | + |
| 38 | +#### Configuration Fields: |
| 39 | + |
| 40 | +- **activityGroupTagString**: Identifier for the Floodlight activity group. |
| 41 | +- **activityTagString**: Identifier for the Floodlight activity. |
| 42 | +- **transactionId**: Unique transaction ID. |
| 43 | +- **revenue**: Total revenue of a transaction. |
| 44 | +- **quantity**: Quantity of items sold. |
| 45 | +- **uVariables**: Additional custom Floodlight variables. |
| 46 | +- **dcCustomParams**: Custom data for event snippets. |
| 47 | + |
| 48 | +--- |
| 49 | + |
| 50 | +### 2. Counter Activity |
| 51 | + |
| 52 | +Track non-monetary conversion data such as unique users, conversions, and session length. |
| 53 | + |
| 54 | +#### Configuration Fields: |
| 55 | + |
| 56 | +- **activityGroupTagString**: Identifier for the Floodlight activity group. |
| 57 | +- **activityTagString**: Identifier for the Floodlight activity. |
| 58 | +- **enableDynamicTags**: Toggle for dynamic tags. |
| 59 | +- **countingMethod**: Conversion counting method (`standard`, `unique`, or `per_session`). |
| 60 | +- **sessionId**: Unique session ID (relevant for `per_session` counting). |
| 61 | +- **uVariables**: Custom Floodlight variables. |
| 62 | +- **dcCustomParams**: Custom data for event snippets. |
| 63 | + |
| 64 | +--- |
0 commit comments