Skip to content

chore: add liquid templating section to customizing destinations #16144

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
luke-belton wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore: add liquid templating section to customizing destinations #16144

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions .../destinations/customizing-destinations.md → ...destinations/customizing-destinations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,22 @@ Or to construct a custom JSON payload that conforms to an existing API specifica

> You can see the full capabilities of templating with our Hog programming language in the [Hog documentation](/docs/hog)

### Using Liquid templating

Destination templates also support [Liquid templating](https://liquidjs.com/filters/overview.html). This is useful for transforming values before sending them to a destination.

<CalloutBox icon="IconInfo" title="Tip: Converting strings to numbers" type="fyi">

Some destinations (like Google Ads) expect numeric values. If your value is stored as a string, you can convert it using Liquid's `plus` filter:

```liquid
{% assign conversionValue = conversionValue | plus: 0 %}{{ conversionValue }}
```

This forces the value to be treated as a number, which is required when a destination's API rejects string-encoded numeric fields.

</CalloutBox>

### Global object

Below is the structure of the global variables available whenever templating a destination.
Expand Down
Loading