Overview

PostUp (Upland) is an enterprise email solution that can be leveraged to target audiences through email, browser push, and on-site engagement. Integrating PostUp with Lytics allows you to keep your PostUp lists up-to-date with relevant user data from Lytics audiences that are enriched with behavioral scores, content affinities, and more.

Authorization

If you haven't already done so, you will need to set up a PostUp account before you begin the process described below. To authenticate this integration, your level of system access should include privileges to perform the following API operations on PostUp:

If you get an error on your workflow that looks like an authentication error, please contact your PostUp site administrator for more information about your user-level system access. If you are new to creating authorizations in Lytics, see the Authorizations documentation for more information.

  1. Select PostUp from the list of providers.
  2. Select the PostUp method for authorization.
  3. Enter a Label to identify your authorization.
  4. (Optional) Enter a Description for further context on your authorization.
  5. Enter your PostUp Username and Password for the authorization.
  6. Click Save Authorization.

Import Audiences & Activity Data

Import PostUp recipients and campaign activity into Lytics to gain insights into your users and campaigns.

Integration Details

  • Implementation Type: Server-side Integration.
  • Implementation Technique: REST API Integration.
  • Frequency: Batch Integration.
  • Resulting data: User Profiles and User Fields.

This integration utilizes the PostUp APIs to import user data. Once the import is started the job will:

  1. If it has been more then 24 hours since the last recipient import:
    1. Iterate through lists.
    2. For each list, request recipients in the list
    3. Ingest the recipients, to the postup_users stream
  2. Request all campaigns
  3. For each campaign, request all the mailings from the past 90 days.
  4. For each of the mailings request a mailing report, of each activity type:
    1. Opens
    2. Unique clicks
    3. Hard Bounces
    4. Soft Bounces
  5. Ingest the tab separated file for each report to the postup_activity stream.

Fields

The following fields are included in the default mapping of the postup_users stream:

Source FieldLytics User FieldDescriptionType
email(address)email unique idEmail Addressstring
recipientIdpu_id unique idPostUp Recipient IDstring
externalIdpu_ext_id unique idPostUp External IDstring
set("email" or "mobile")channelsAll Channels Used (web, email, etc.)[]string
emaildomain(address)emaildomainEmail Domainstring
carrierpu_carrierPostUp carrierstring
set(list_catagory)pu_categoriesPostUp List Categories[]string
commentpu_commentstring
dateJoinedpu_joined_datePostUp Date Joineddate
set(list_id)pu_list_idsPostUp List IDs[]string
set(list_title)pu_list_titlesPostUp List Titles[]string
sourceSignupDatepu_source_signup_datePostUp Date Signed Up Sourcedate
statuspu_statusstring
dateUnsubpu_unsub_datePostUp Date Unsubscribeddate

The following fields are included in the default mapping of the postup_activity stream:

Source FieldLytics User FieldDescriptionType
recipientIdpu_id unique idPostUp Recipient IDstring
email(address)email unique idEmail Addressstring
externalIdpu_ext_id unique idPostUp External IDstring
set("email" or "mobile")channelsAll Channels Used (web, email, etc.)[]string
emaildomain(address)emaildomainEmail Domainstring
valuect(hash(urlmain(url_clicked)))hashedurlsHashed Urls Visitedmap[string]intsum
map("email" or "mobile", epochms())last_channel_activitiesLast Activity By Channelmap[string]time
bounce_reasonpu_bounce_reasonPostUp Last Bounce Reasonstring
count(event_type)pu_click_ctPostUp Click Countint
map(campaign_id,1)pu_click_ct_by_campaignPostUp Campaign Click Countmap[string]int
valuect(hourofday())pu_hourly_openPostUp Hourly Opensmap[string]intsum
valuect(hourofweek())pu_hourofweekPostUp Hour of Week Opensmap[string]intsum
epochms()pu_last_click_tsPostUp Last Clickdate
urlmain(url_clicked)pu_last_click_urlPostUp Last URL Clickedstring
epochms()pu_last_open_tsPostUp Last Opendate
valuect(yymm())pu_monthlyPostUp Opens By Monthmap[string]intsum
count(event_type)pu_open_ctPostUp Open Countint
map(campaign_id,1pu_open_ct_by_campaignPostUp Campaign Open Countmap[string]int

Configuration

Follow these steps to set up and configure an import of PostUp in the Lytics platform. If you are new to creating jobs in Lytics, see the Data Sources documentation for more information.

  1. Select PostUp from the list of providers.

  2. Select the Import job type from the list.

  3. Select the Authorization you would like to use or create a new one.

  4. Enter a Label to identify this job you are creating in Lytics.

  5. (Optional) Enter a Description for further context on your job.

  6. Complete the configuration steps for your job.
    postup config

  7. In the Site ID text input, enter your PostUp site ID. It can be found at the bottom of the Server tab in the PostUp UI

  8. PostUp site-id

  9. Click Start Import.

Export Audiences

Improve and refine your email targeting on PostUp by exporting Lytics audiences containing real-time, event-driven recipient updates.

Integration Details

  • Implementation Type: Server-side Integration.
  • Implementation Technique: Audience Trigger Integration
  • Frequency: Real-time Integration.
  • Resulting data: Updates to users in Lytics are transmitted to PostUp lists. New recipients are added, existing recipients are updated. Recipients are never removed from PostUp lists.

This integration utilizes the PostUp REST API to create and update recipients in PostUp lists.

  1. If no existing PostUp list is specified, one will be created.
  2. As users enter the Lytics audience being exported, they will be created and added to the PostUp list.
  3. If users are exiting the selected Lytics audience, you can configure the job to remove users from PostUp list.
  4. User updates are pushed to PostUp in batches via the PostUp import endpoint. As users are updated in Lytics, updates are pushed to PostUp and the selected field mappings are modified.

Fields

By default, Lytics exports the following field to PostUp:

Lytics User FieldDescription___ FieldType
emailEmail AddressEmailstring

Lytics fields can be mapped to a selection of standard PostUp fields. You can also map to custom PostUp fields, which must be first created in PostUp:

  1. From the PostUp main menu, select Settings.
  2. Select Custom Fields.
  3. At the bottom of the page, under Add New Field, type your field name and select the appropriate type (note: Lytics does not support types Currency and Single Character).
  4. Click Save.

In the Lytics UI, select field mappings as described in step 11 below.

Configuration

Follow these steps to set up and configure an export of an Audience in the Lytics platform. If you are new to creating jobs in Lytics, see the Destinations documentation for more information.

  1. Select PostUp from the list of providers.
  2. Select the Export Audiences job type from the list.
  3. Select the Authorization you would like to use or create a new one.
  4. Enter a Label to identify this job you are creating in Lytics.
  5. (Optional) Enter a Description for further context on your job.
  6. Select the audience to export.
  7. Complete the configuration steps for your job. postup-export
  8. Audience: select the Lytics audience to sync to a PostUp list.
  9. PostUp List: (optional) select the PostUp list to update. If no list is selected, a new list will be created in PostUp called "Lytics + audience tag".
  10. Email Field: Lytics field name that contains the user’s email. The Lytics Email Address is the default.
  11. Identifier Field Mapping: (optional) select the Lytics fields you would like to export, along with your desired corresponding PostUp fields.
  12. Remove Subscribers from List: (optional) check to remove a user from the selected PostUp list when that user exits the selected Lytics audience.
  13. Click Start Export.