Mandatory fields in a request to perform routing
In order to be usable in a campaign on Sendingly, the request must contain the recipient's channel in a field named EMAILor MOBILE.
Required fields to query the send table
In order for the final campaign to be queryable from the send and reaction tables, the query must contain:
-
- the recipient's ID in a field named SYS__CUSTOMER_ID
- the recipient's brand ID in a field named SYS__BUSINESS_UNIT_BRAND_ID
- the recipient's country ID in a field named SYS__BUSINESS_UNIT_COUNTRY_CODE
Prefix fields
If some fields are not prefixed properly, the calculation will go into error.
Add an alias to subqueries
Like field prefixes, it is mandatory to add an alias to subqueries to avoid errors.
Reference table joins
In the case of a join with a reference table containing multiple brands and/or countries, it's important to add the fields business_unit_brand_id and business_unit_country_code in the join.
The unique customer ID join key
When using the unique customer ID as a join key, it is necessary to systematically add a condition on the field is_master = true.