This article describes how to configure PebblePost in your Tag Management account.
Tag configuration
Go to the tag marketplace to add a new tag. For more information, see About tags.
When adding the tag, configure the following settings:
- PebblePost Marketer ID: This will be an integer value provided by PebblePost. For example:
123456.
Load rules
Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation.
Recommended Load Rule: All Pages
Data mappings
Data mappings send values from data layer variables to the corresponding variables in the vendor tag. For more information, see About data mappings.
The destination variables for the PebblePost Tag are built into its Data Mapping tab. Available categories are:
Standard
| Destination Name | Description |
|---|---|
| Customer Email (email) | The email address for the customer. |
| Synthetic Endpoint (end_url) | The URL trigger for the transaction. The PebblePost tag triggers campaign logic based on URL value, if your page will not provide one, you may pass an artificial URL value here. For example: “/thankyou”. |
| Customer Tag (tags) | A custom value you may pass through the PebblePost tag. |
E-Commerce
Because the PebblePost Tag is e-commerce enabled, it will automatically use the default E-Commerce Extension mappings. Manually mapping in this category is generally not needed unless:
- You want to override any Extension mappings
- An e-commerce variable you want is not offered in the extension
| Destination Name | Description |
|---|---|
| Order ID (order_id) | The ID for the order being placed. |
| Order Total (order_total) | The total for the order being placed. |
| Customer Id (customer_id) | The ID of the customer making the order being placed. |
This page was last updated: November 10, 2026