Macros with REPLACEMENTS.
This article describes replacements functionality and explains with what custom parameters and how it can be used.
Macros with Replacements allows to pass parameters from the supply to demand.
Macros and Replacements can also be used to gather data to the Aniview reporting system via the usage of Custom Dimensions(Core Settings | Custom Params).
Example use case
The client is sending AV_CONTENT_TITLE, AV_TITLE or content_title in parallel depending on request, but want to group all of the values in the reporting under one custom dimension. (There may be few reasons why to send the same data under different parameters like different versions of the client’s software or other client-related specific use cases).
Most of the times it happens due to old integrations.
It is better to use the original macro such as AV_CONTENT_TITLE
In the above case the Replacements(which are the available macros) will have the following structure:
AV_CONTENT_TITLE = query_parameter.AV_TITLE
or query_parameter.AV_CONTENT_TITLE
or query_parameter.content_title
The above example means that [AV_CONTENT_TITLE] macro will be resolve from AV_TITLE= or AV_CONTENT_TITLE= or content_title=
From the query string of the serving request.
List of Macros with REPLACEMENTS
We have 5 special custom parameters AV_CUSTOM17 - AV_CUSTOM21, that knows how to resolve data from the resolved REPLACEMENTS.
You can add custom parameters in Account Settings > CUstom Parameters or use the instruction below: Core Settings | Custom Params.