Skip to content

Commit 3a8e31b

Browse files
committed
fix numbering
1 parent ed0128e commit 3a8e31b

File tree

1 file changed

+5
-5
lines changed
  • src/connections/destinations/catalog/actions-google-campaign-manager

1 file changed

+5
-5
lines changed

src/connections/destinations/catalog/actions-google-campaign-manager/index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,11 @@ When you have Segment installed and enable this destination, Segment takes care
2121

2222
## Getting Started
2323
Before you connect Segment to Google Tag for Campaign Manager, ensure you have set up your Floodlight configurations in Campaign Manager.
24-
2. Navigate to the Segment web app, select Connections, then click on Destinations.
25-
3. Search for "Google Tag for Campaign Manager" in the Destinations Catalog and click on the destination.
26-
4. On the destination's overview page, click **Add destination**.
27-
5. Select the appropriate source that will forward data to Campaign Manager and click **Next**.
28-
6. On the Setup page, give your destination a name and click **Create destination**.
24+
1. Navigate to the Segment web app, select Connections, then click on Destinations.
25+
2. Search for "Google Tag for Campaign Manager" in the Destinations Catalog and click on the destination.
26+
3. On the destination's overview page, click **Add destination**.
27+
4. Select the appropriate source that will forward data to Campaign Manager and click **Next**.
28+
5. On the Setup page, give your destination a name and click **Create destination**.
2929
6. On the Settings tab:
3030
* Enter the Advertiser ID found under Floodlight > Configuration in Campaign Manager.
3131
* Set **Allow Ad Personalization Signals**, if needed.

0 commit comments

Comments
 (0)