Marketing Areas Concept

At the start there will be a 1:1 relation between data object and marketing area, but in the future a 1:n will be possible. For an In-app campaign we only see the use case for a 1:1 relation. For other data objects like contacts we still have to support the 1:n relation.

With the Marketing Area API or an UI feature service In-app can check whether marketing areas are enabled for the customer. If enabled UI should use the Marketing Area Select so that the marketer can choose the marketing area for the campaign.

It is not yet decided if an application will have marketing areas assigned. If yes then an In-app campaign can only be use a sub-set of marketing areas of the application.

A campaign has zero (no use of marketing areas) or one marketing area assigned to it, i.e. we have to add the marketing area to the PostgreSQL and BigQuery campaign tables. When a customer has marketing areas enabled In-app service has to query just the campaigns with the these marketing areas. In fact the backend has to take care of marketing areas in every query used by an endpoint so that In-app only shows campaigns which the marketer has access to.

Client service will include the marketing areas of a contact in the contact token. DES will use these to filter campaigns.

Only the segments with the marketing area assigned to the campaign should be selectable by the marketer.

Automation programs and RTI will ask for campaigns with certain marketing areas which we have to support.

No changes to SDS will be needed because a segment already has a marketing area assigned to it and SDS does not deal with metadata of a segment.