Create a campaign with a segment table

Who can use this feature?

  • Global admins, SuccessBLOC owners, and collaborators
  • Users have view access to SuccessBLOCs that are published to a team; additional access permissions to individual SuccessPlays, campaigns, canvas, and objective templates vary.
  • Available on all plans

The segment table component of a campaign allows you to display data in a tabular format, related to a campaign target. Unique to segment tables, you can optionally set some filter conditions based on dynamic data.

Suggested uses

Use segment tables to streamline customer communications for the following scenarios:

  1. Subsidiary contract renewals approaching: Show the key contacts at headquarters (parent / ultimate parent company) all of the upcoming renewals for the subsidiary accounts (children companies).
  2. Top users of a particular feature: Show the key contacts at all subsidiaries (sibling companies) the the top 10 users with the most usage among Product 3.
  3. Collection records for an account: Show all professional service projects (custom collection data) associated with an account—dynamically filtered by the recipient's preferred package type.

To create a segment table, simply add the Segment Table component of a campaign:

All other campaign settings, such as subject and sender, target user segment, schedule, goal, and advanced settings are available to configure just as any other campaign.

About dynamic data in filters

Dynamic data is available for text and ID values when filtering segment tables. Rather than specifying the value you want to use (e.g., Parent ID = 12345), dynamic data allows Totango to choose the value based on who the email recipient is (e.g., Parent ID = 'Targeted: Account ID'). See dynamic data examples for each type of segment object below.

Supported filters

Dynamic data may be available for any system text attribute (e.g., ID, name). Lifecycle attributes are not supported. Due to the sensitive nature of some data, the system's default behavior limits the number of attributes available for dynamic data; however, if your business case requires dynamic data for an attribute that is currently restricted, please contact support.

Dynamic Data options appear in different areas, depending on the attribute type.

Example - ID field:

Example - Name field:

Supported objects

Segment tables support the following objects: Accounts, users, opportunities, collection. Consider the following examples for flat or multi-level hierarchies.

Flat:
1-level.png

Multi-level:
2-level.png

Accounts example

Subsidiary contract renewals approaching: Gene from Acme headquarters is targeted for the campaign; the resulting email sent to him contains account data from direct children of Acme (e.g., Acme - West, Acme - East) where contract renewal date is in the next 90 days.

Users example

Top users of a particular feature: Stan from Acme - West is targeted for the campaign; the resulting email sent to him contains user data from any sibling account (e.g., Acme - East) where user has visited the dashboard greater than or equal to 20 times in the last 14 days.

Collection examples

Specifying the account ID using dynamic data is not always necessary (e.g., ID = 'Targeted: Account ID'. Collections already belong to a specific account, so Totango ensures that you'll never expose collection information to a recipient outside of the account (flat hierarchy) or parent account (multi-level hierarchy). If you want to ensure the collection data is only shown to a particular branch of the hierarchy, then we recommend specifying account ID via dynamic data.

Account ID not specified:

  • Account with flat hierarchy: Gene from Acme is targeted for the campaign; the resulting email sent to him contains collection data for Acme (e.g., all projects where type = Training).
  • Account with multi-level hierarchy: Stan from Acme - West is targeted for the campaign; the resulting email sent to him contains collection data for Acme parent and all its children accounts Acme - West, Acme - East (e.g., all projects where type = Training).

 

Account ID specified:

  • Account with flat hierarchy: Specifying dynamic data is unnecessary. Gene from Acme is targeted for the campaign; the resulting email sent to him contains collection data for his account (e.g., all projects where type = Training).
  • Account with multi-level hierarchy: Stan from Acme - West is targeted for the campaign; the resulting email sent to him contains collection data for only Acme - West (e.g., all projects where type = Training).

 

Other dynamic data filters specified:

In addition to the flat or multi-level hierarchy logic detailed above, you can use dynamic data for some collection attributes (text) other than Account ID. In this example, Stan from Acme - West has a user attribute for Package = Hourly Subscription. Maggie from Acme - East has a user attribute for Package = Managed Services.

Within the segment table properties for the selected collection (Projects), the collection attribute "Package" can be set to dynamically use the value of the user's "Package" attribute (e.g., Package: 'Targeted: Package').

  • Stan from Acme - West sees all projects from Acme - West, filtered by his package value (e.g., all projects where type = Training and package = Hourly Subscription).
  • Maggie from Acme - East sees all projects from Acme - East, filtered by her package value (e.g., all projects where type = Training and package = Managed Services).

Not filtering by dynamic data

Totango will only allow sharing records that belong to the targeted user's account(s), regardless of dynamic data technique used. However, Totango will prompt you as a precaution when do not use a dynamic data filter to avoid unintended or confusing emails to your targeted list.

Configure a segment table component

To add a segment table component, edit an existing campaign or create a new campaign.

  1. Open the campaign designer from your campaign.
  2. Click-and-drag the Segment Table component to the email body. (Or click on an existing segment table component to view properties.)
  3. Click on the component to configure properties.


    Source
  4. Data Type: Choose the segment object (accounts, users, opportunities, collection). Upon send, the available data set is limited per campaign target. 

    Example: Joe from Acme is targeted for the campaign; his email only contains account or contact/user data related to Acme.

  5. Filters: Click to add filters to refine the available data set for the table. Text and ID attributes* allow you to choose from the following: Any Value, No Value, or Dynamic Data (e.g., parent_id: 'Targeted: Account ID').

    See "About dynamic data filters" above for examples for each object type.


    Table Configuration
  6. Edit Columns: Choose the attributes to include in the table.
  7. Column Names: Optionally choose a custom display name for each attribute, as it will appear in the table heading (e.g., customer-facing, shortened, etc.)
  8. Sort Column: Choose the column used for sorting the table. Options depend on data type of sort column (e.g., alphabetical/reverse, highest/lowest).
  9. # of Rows: Specify the maximum number of rows to include in the table (cannot exceed 100). If more rows of data are available beyond the maximum specified, Totango adds a message to the bottom of the table to indicate that more rows are available but not included in the email (e.g., X rows out of XX are shown).
  10. Fallback text: Enter text to show if table has no data (e.g., No data to display).

    Appearance
  11. Configure the display settings of the table:
    • Display text color
    • Font (px)
    • Font Size
    • Border color (hex)
    • Top row color (hex)
    • Component's padding (top, bottom, left, right) 
  12. Click Save.
  13. Click Preview and to send a test email for review, featuring data for one of the campaign targets.

When the campaign sends according to the schedule, each recipient receives an email with a table displaying data related to their account / user records, according to the filters specified.

FAQs

Question: I created a dynamic filter, but when I preview the email the table is empty. I checked the filters and they look correct. What's happening?

Answer: This behavior may occur when there is a type mismatch. Please, contact our support to review the campaign.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request