Once the Audience Management setup has been completed, your site will optionally sync additional reader data to the connected email service provider (ESP) based on their activity around the site. This extra data can help you with off-site marketing and automations: some examples of how some Newspack publishers use this tool include:
- Email campaigns targeting paid subscribers or donors
- Special offers for readers with registered accounts but no active paid subscription
- CRM integrations to organize contacts based on their registration method, status, or UTM parameters
Reach out to your TAM to discuss other possibilities for how to use this enhanced data.
Configuring fields and sync behavior
Once Audience Management setup has been completed, you can navigate further down the Audience -> Setup page to configure the fields that are synced to the connected ESP.
The following options are available for all supported ESPs:
- Sync contacts to ESP: This top-level toggle lets you enable or disable contact data syncing entirely. If Audience Management is enabled on your site, this will be enabled by default, but you can change the setting at any time.
- Metadata Field Prefix: This prefix will be prepended to all field names before syncing. This helps avoid naming conflicts with existing fields and potential data loss from such conflicts. The default value is
NP_for “Newspack”. - All fields are enabled by default, but you may not need all of the data for your own marketing or CRM purposes. Uncheck the boxes for any fields to disable them in future syncs.
For sites connected to Mailchimp or ActiveCampaign, there are some additional settings:
- Audience ID (Mailchimp) or Master List (ActiveCampaign): Selecting an audience or list here will allow contact data to be synced to the ESP even if the reader did not explicitly sign up for any newsletters.
- Default Reader Status (Mailchimp only): If an Audience is selected, readers who are added to the audience but haven’t explicitly signed up for any newsletter contact lists will be added with this status. Which status you choose might depend on the local privacy laws governing your site. If you’re unsure if local laws allow contacts to be emailed without explicit permission, please leave this set to Transactional.
- Subscribed means the contact can be contacted for marketing purposes.
- Transactional means the contact has not given explicit permission to be contacted, and cannot be contacted for marketing purposes.
Data fields
These are the fields that Audience Management currently syncs to the connected ESP. We use our internal Data Events API to trigger sync requests when readers take specific actions such as registering for an account, logging in, or completing a transaction via WooCommerce.
Basic fields
These fields describe basic info about the contact. The values in these fields will rarely change.
| Field name in ESP | Description | Example | When is this field synced? |
|---|---|---|---|
| First Name | Reader’s first name | Reader | |
| Last Name | Reader’s last name | Name | |
| Reader’s email address | reader.name@example.com | ||
| NP_Account | WordPress user account ID of reader | 323 | reader_registeredFor ActiveCampaign only: When there is an update on the list of lists the contact is subscribed to ( newspack_newsletters_update_contact_lists) |
Registration fields
These fields describe the context of when a reader registers for a new account. For example, if UTM parameters are present on the URL when the reader registers for an account, these parameters will be captured in the Signup UTM fields.
| Field name in ESP | Description | Example | When is this field synced? |
|---|---|---|---|
| NP_Registration Page | URL of page reader reader signed up at | https://example.com/home | reader_registered |
| NP_Registration Date | Date reader registered in MM/DD/YYYY format | 09/19/2022 | reader_registered |
| NP_Registration Method | backfill-script newsletters-subscription registration-block-content-gate woocommerce auth-form registration-block registration-block-popup | reader_registered | |
| NP_Signup UTM: source | UTM source if present when reader registers | test+source | reader_registered |
| NP_Signup UTM: medium | UTM medium if present when reader registers | test+medium | reader_registered |
| NP_Signup UTM: campaign | UTM campaign if present when reader registers | test+campaign | reader_registered |
| NP_Connected Account | SSO service used to register if user registered with a supported service (e.g. Sign in With Google) | reader_registered, reader_logged_in | |
| NP_Network Registration Site | For sites using Newspack Network only. Shows the full URL of the site that the reader registered on. | https://www.networksite.com/ | new_network_reader, network_reader |
Status fields
These fields describe a reader’s current state in some way. These values might change over time.
| Field name in ESP | Description | Example | When is this field synced? |
|---|---|---|---|
| NP_Woo Team | For sites using Newspack Network + Teams for Woo Memberships only. a comma separated list of the Woo Membership Teams the reader is a part of, if any. | Newspack’s team | new_network_reader, network_reader |
| NP_Newsletter Selection | Comma-delimited list of the newsletter lists this reader is currently subscribed to. | List Name, Segment 1, Segment 3 | newsletter_subscribednewsletter_updated |
| NP_Total Paid | Lifetime total amount the reader has donated through Newspack’s WooCommerce system. | 120 | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
Current Product fields
These fields describe a reader’s transactional activity via WooCommerce on your site. Because a single reader may have made multiple different types of transactions, we limit these fields to describing what we call the reader’s current product:
- The reader’s most recently started active subscription (either recurring donations or non-donation subscriptions)
- If no active subscription, the most recently started inactive subscription with a cancelled or expired status
- If no subscriptions at all, the most recent one-time donation (non-recurring, non-donation transactions are ignored).
| Field name in ESP | Description | Example | When is this field synced? |
|---|---|---|---|
| NP_Current Subscription Start Date | Start date of current subscription | 09/19/2022 | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Current Subscription End Date | End date of current subscription, if the subscription will end | 09/19/2023 | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Membership Status | If it’s a donation, will be One of: Monthly Donor, Yearly Donor, Ex-Monthly Donor, Ex-Yearly Donor, or Donor (this last one is used for donors without a recurring subscription e.g. one-time donation) If it’s a non-donation subscription, it Can be any valid subscription status: ‘active’, ‘on-hold’, ‘pending’, ‘cancelled’, ‘expired’, ‘pending-cancel’ If the reader has no donations or subscriptions but has non-donation, non-recurring purchases, it will be “customer” | expired Yearly Donor Ex-Monthly Donor customer | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Last Payment Amount | Amount of last payment | 15 | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Last Payment Date | Date of last payment in MM/DD/YYYY format | 09/19/2022 | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Next Payment Date | Date of next payment in MM/DD/YYYY format | 10/19/2022 | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Billing Cycle | Frequency. One of: month, year | month | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Recurring Payment | Amount of recurring payment (the value of each payment, not the sum of all payments) | 15 | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Product Name | Name of donation or product reader purchased | Donate: Monthly Supporter | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Payment Page | Page reader checked out on | https://example.com/support-us | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Payment UTM: source | UTM source of payment page if present | test+source | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Payment UTM: medium | UTM medium of payment page if present | test+medium | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
| NP_Payment UTM: campaign | UTM campaign of payment page if present | test+campaign | reader_logged_inorder_completeddonation_subscription_changedproduct_subscription_changed |
Engagement Table of Contents
- Newspack Campaigns
- Newsletter Sign-Up
- Newspack Newsletters
- Newsletter Subscription Form Block
- Social
- Listings
- Audience Management
- Audience Management Content Gating
- Republication Tracker
Audience Management Table of Contents