List of supported macros and parameters
This section outlines the macros and parameters supported by our system.
Macros
Macros are replaced by the system with specific values on our backend side during link generation. You don’t need to fill them in manually.
Unique event identifier exid
This macro is replaced with the UUID of a specific event. It’s used for tracking, analytics, and postbacks.
Example:
https://example.com?sub1={exid}
Note: This parameter is mandatory and should always be listed first.
Bundle ID of the mobile application
This macro is replaced with the bundle identifier of the mobile application.
https://example.com?sub1={exid}&sub2={bundle}
Macro fbclid
The fbclid macro is used for the automatic insertion of the Facebook click identifier.
https://example.com?sub1={exid}&sub2={fbclid}
User Agent Macro ua_raw
The ua_raw macro is used to insert the user's original user agent, including information about their device, browser, and operating system.
https://example.com?sub1={exid}&sub5={ua_raw}
Macros of the Splits section
Triggered rule identifier rule_id
Substitutes the ID value of the rule that was triggered during the event.
Example:
https://example.com?sub1={exid}&sub2={rule_id}
Triggered rule name rule_name
Substitutes the name of the rule that was triggered.
Example:
https://example.com?sub1={exid}&sub3={rule_name}
Parameters
Parameters are set manually and are written in the final link used for upload.
Pixel ID pixel_fb
When creating a flow, the specified pixel is automatically written to the parameters of the final link. However, you can also manually specify which Facebook or TikTok pixel should receive the event data.
Before using pixel_fb in a link, make sure that the desired pixel is saved in the Pixels section in your ZM apps account.
Example:
https://example.com?sub2={sub2}&pixel_fb=384927561034275
Application key app
Defines which application should be shown. Used to repalce the bundle of the application or the hash ID of the selected PWA.
Example:
https://example.com?sub2={sub2}&app=id6746545668
If your bundle ID includes a "tail", for example: id6747820731?ppid=9c8c173, then you must specify the full value in app parameter.
For example: https://example.com?sub2={sub2}&app=id6747820731?ppid=9c8c173.
If you specify only id6747820731, the application will not be recognized.
When using application splitting in a flow (distributing traffic across multiple apps), the app parameter overrides the split logic.
This means all users will be directed to the app specified in the app parameter, regardless of any split settings.