Setting the sync field for audience information

When you complete a test run or a production run, audience information is exported by Unica Campaign to Acoustic Campaign. For the Email and Push processes, you can specify the fields that must be used as sync fields for the audience information.

Setting sync fields for audience information

For the Email and Push processes, the Unica CampaignaudienceId is used as the sync field by default. For the SMS process, the phone number is used as the sync field.

To set the sync fields, go to the Field mappings tab of the Email or Push process. Select the Fields to export to Acoustic Campaign and complete the mapping. Click the check mark checkmark in the Sync column for the field or fields that are to be used as the sync fields.

Consider the following points about the sync fields and the uploading of data to Acoustic Campaign:
  • If the combination of sync fields results in a unique record, the audience data is uploaded to Acoustic Campaign as new audience data.
  • If the combination of sync fields does not result in a unique record, the existing audience data is updated in Acoustic Campaign.
  • The Email and MobileUserIDs are case sensitive.
  • campaignaudienceId is uploaded to Acoustic Campaign even if other fields are selected as sync fields.
  • The response from Acoustic Campaign also contains the campaignaudienceId. Changing the sync field does not change the response tracking mechanism for the Email process.
  • Duplicate records are considered as valid records and so they do not affect the allowableFailurePercentage for a process box.
Note: If you are using a keyed (restricted) database, any sync fields that are specified are ignored and only the key field is used for uploading data to Acoustic Campaign.
Note: If the Campaign table is mapped with an audience level of type text, the EnableSelectOrderBy property must be set to False. For more information, see the Configuration properties in the Unica Campaign Administration Guide.

The campaignaudienceId field

When you complete a test run or a production run, audience information is exported by Unica Campaign in one special field, campaignaudienceId. Consider the following points about the campaignaudienceId field:
  • When contact data is uploaded to the Acoustic Campaign database for the first time, a campaignaudienceId column is added to the database. This campaignaudienceId field is the lookup key by default.
  • The campaignaudienceId is populated in the Acoustic Campaign database only when the contact data upload is initiated from Campaign.
  • After the campaignaudienceId column is added, the audience information is uploaded to this column when contact data is uploaded.
  • The campaignaudienceId is included in each event that is sent by Acoustic Campaign to UBX for contacts. For example, emailSend, emailOpen, emailBouce, emailClick.
  • You cannot map the campaignaudienceId database column from the Field mappings tab of the Email process. The campaignaudienceId database column is updated internally.
  • When the SMS process is run, the campaignaudienceId is populated in the UA_SENTSMS and UA_INTERACTEDSMS system tables after the time specified for the sleepIntervalInMinutes property for the Event Download Schedule. The campaignaudienceId is also populated in the respective contact list in the Acoustic Campaign database as mentioned in SMS process.
  • When the Push process is run, the campaignaudienceId is populated in the UA_SIMPNOT_APPOPENED, UA_SIMPNOT_URLCLICKED, and UA_MOB_PUSH_SEND system tables after the time specified for the sleepIntervalInMinutes property for the Event Download Schedule. The campaignaudienceId is also populated in the respective contact list in the Acoustic Campaign database as mentioned in Push process.
  • The format for the campaignaudienceId is AudienceName~#field1Name~#fieldValue~#field2Name~#fieldvalue~#fieldnName~#fieldvalue.

    For example, Customer~#CustomerID~#20.