Default attributes

Sending campaigns from Amperity to downstream marketing workflows is a combination of:

  • A segment that defines the audience that you will use with your campaign.

  • A campaign that breaks that audience down into sub-audiences that align to your marketing strategies and goals.

  • A set of destinations that specify the locations and channels to which you will send each sub-audience.

    Most destinations may be configured to send a list of attributes (this topic) that are specific to your brand’s use cases.

Default attributes are configured from the Campaigns page. Each destination may be configured to send a list of attributes that your brand can use with a variety of downstream workflows, such as audience matching, customer activation, paid media workflows, or measuring campaign results using offline events.


For many downstream marketing applications the names of attributes are not arbitrary. There are often specific requirements for names of attributes and the data that may be associated with each attribute.

For example, the name of the field for an email address attribute may be case-sensitive, such as “email”, “Email” or “EMAIL”. Many downstream marketing applications require email addresses to be converted to a SHA-256 hashed value.

Review the documentation for individual destinations to verify if additional non-default attributes may be configured, and then sent alongside the default attributes.

The following sections describe the steps you’ll follow to configure the default attributes for individual destinations.

Step 1.

Default attributes for each destination are configured from the Campaigns page. Click the Campaign settings link next to the Create campaign button to open the editor from which you can configure default attributes.

Configure default attributes for destinations.
Step 2.

Choose the Default attributes tab, and then from the Database drop-down, select the database that contains the attributes that your brand sends to downstream workflows.

Then from the Destinations drop-down, choose the destination for which default attributes will be configured.

Step 3.

After you have selected a database and a destination, a list of attributes is shown. For example, the list of attributes that may be sent to Meta Ads Manager:

The list of default attributes for a destination.


A destination can have very specific requirements for the names of fields and the values each field may contain.

For example, some destinations:

  • Only accept email addresses (or SHA-256 hashed email addresses).

  • Require email addresses, but also accept a larger set of optional attributes.

  • Require attributes to be mapped to specific naming patterns, such as “email”, “Email” or “EMAIL” before they can be accepted.

For destinations that use an API, Amperity pre-configures the list of attributes that are required and/or are optional. Review the Amperity documentation for each destination to understand which attributes may be configured.

For destinations that accept files—SFTP, Amazon S3, Azure Blob Storage, and Google Cloud Storage—your brand should verify the requirements for the downstream system to which data will be sent before configuring default attributes.

Step 4.

When default attributes are ready, click the Save button in the lower right corner of the Default attributes page.


Be sure to verify the names of the fields and the values that appear within each field in the downstream system. This will ensure that Amperity is sending the right data and can support your brand’s use cases.