Attentive — Update Subscriber Attributes

Write custom attributes to an Attentive subscriber as soon as Amperity sees the customer interaction, using the custom attributes endpoint. The attributes are stored on the subscriber, appear under Settings > Custom Attributes in Attentive, and can be used in the Attentive segment builder. This connector does not send an event.

To trigger an Attentive journey, use the Attentive — Send Custom Event connector instead. That connector can also write subscriber attributes before it sends the event. To send customer attributes on a schedule rather than in real time, use the Attentive API destination.

This connector sends from a real-time journey. See Real-time destinations.

Credentials

This connector uses the same credential type as the Attentive API destination and the Attentive — Send Custom Event connector. You can reuse one of those credentials here if its API key has the scope listed below.

Name and description

The name and description for a credential.

API key

Required. An API key for a custom app in your Attentive account. Amperity sends the key as a bearer token with each request. See Create and manage custom apps in the Attentive documentation.

The API key must have the attributes:write scope.

Settings

Name and description

The name and description for a destination.

Business user access

By default a destination is available to all users who have permission to view personally identifiable information (PII).

Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies.

Enable the PII setting checkbox to allow limited access to PII for this destination.

Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows.

Activate node settings

The rest of the configuration for this connector belongs to the journey that sends to it. Add this destination to an Activate node, then configure the following fields on that node. Two nodes may send to the same destination with different identifiers and attributes.

Email, Phone number, and Client user ID

The Amperity attributes that identify the subscriber in Attentive. Map at least one; a send with no identifier mapped fails.

  • Email is the subscriber’s email address.

  • Phone number must be in E.164 format, including the country code, such as “+15551234567”.

  • Client user ID matches only subscribers that Attentive has already associated with that ID through its Identity API.

Mapping more than one identifier tells Attentive that they belong to the same person, and Attentive associates them on one user. The identifiers are not tried one after another as fallbacks.

Subscriber attributes

Required. The custom attributes written to the subscriber. Map at least one; a send with no attributes mapped fails.

Two Attentive behaviors affect these writes, and Amperity cannot change either:

  • Attentive sets the type of each attribute from the first value it receives. Amperity cannot set the type in advance.

  • An attribute created in Attentive with a fixed list of allowed values rejects any value that is not in the list.