Audience Sync
About Audience Integration
Newscycle Circulation and Newscycle Audience can share occupant and address data, giving Audience a richer dataset for targeted content serving and ad serving on the newspaper website, as well as campaign generation.
Circulation occupant, address and subscription data can be loaded into Audience as source data via an API, and Audience can then send back selected profiles in a flat file, which can be imported via ListMatch and used to target profiles for campaigns in Circulation. For example, profiles for frequent website readers can be imported into Circulation via LM and targeted for a campaign to sell digital subscriptions.
Audience will use the occupant ID as a unique key for storing information about the occupant, including e-mail address, addresses, and subscription info. Once interfaced, occupants can be included in target profiles, allowing certain ads and content to be displayed on the publication website when the occupant logs in. Occupants can also be selected for marketing campaigns.
Initially, you may have your existing Circulation address/occupants loaded into Audience via a flat file, with the assistance of NEWSCYLE Professional Services. In addition, if you store demographic information in Circulation and would like to interface that data to Audience, if the demographic answers have an answer type of “Character” and the Map to Audience field in Demographic setup is set to “y” (see Demographic in the Setup Manual). After the initial load and setup is complete, you can update Audience with new or modified address/occupant information using an incremental sync.
Circulation data can be sent to the Audience API via the Audience Sync option.
Running Audience Sync
The Audience Sync option is used to export occupant, address, subscription, and demographic information from Circulation in a form that can be imported into Newscycle Audience. It can also be used to update incremental changes to occupant, address, subscription, and demographic information to Audience, either directly via a web service call or via export/import as done with the full export.
The file will be named audgenome.xml and be exported to /pbs/exchange/cm/. See Appendix B for the XML format and output examples.
The host name, URL, class path and WSDL used to communicate with the Audience web service are defined by Business Rules in the Audience section of Household Management. Business Rules also control the batch size of the web service call, whether passwords are interfaced, whether only subscribers are interfaced and, if so, which publications they are interfaced for, whether only one profile should be sent per occupant, and other settings pertaining to Audience Sync.
To run the Audience Sync utility:
Select Audience Sync from the Audience menu in Graphical Utilities. The Audience Sync screen displays.
Click the Add button and enter the following fields.
| Field | Type | What to enter |
|---|---|---|
SYNC TYPE | predefined | Enter Full or Incremental. A full sync will export all audience information. An incremental sync will export only audience information that has changed since the last sync. |
ERROR PROFILES | predefined | Indicate "Yes," "No," or "Only" whether the sync should include error profiles. |
SYNC STYLE | predefined | Indicate whether the sync should be Direct or Export. A direct sync is performed via a web service call to Audience. An export sync will export audience information to a file. |
MAXIMUM PROFILES | integer | This field controls the maximum number of records exported. To export all records, leave this field blank or set it to 0. |
LAST SYNC | display | The date and time of the last sync is updated whenever all profiles (Max Profiles left blank) are exported. When a subset of profiles is exported, the date and time are not updated. |
Select Accept to perform the audience sync.
Last updated
