Attentive Tag Destination Config Reference

Attentive Tag is an SMS and email marketing destination. RudderStack sends identify and track events to Attentive to subscribe users and record their activity.

In an Attentive Tag destination spec:

• type: attentive_tag
• definition_version: 1

Sample configuration

version: rudder/v1
kind: destination
metadata:
  name: attentive-prod
spec:
  id: attentive-prod
  display_name: Attentive Production
  type: attentive_tag
  definition_version: 1
  enabled: true
  config:
    api_key: "{{ .ATTENTIVE_API_KEY }}"
    sign_up_source_id: "123456"
    enable_new_identify_flow: false

    connection_mode:
      web: cloud
      cloud: cloud
    consent_management:
      web:
        - provider: oneTrust
          consents:
            - marketing

The above example keeps the legacy subscription flow for identify calls. sign_up_source_id is written as a quoted digit string — see Connection.

Config keys

config accepts only the keys listed below. The shared config key rules cover unknown keys, defaults, and immutability.

Attentive Tag accepts only identify and track events. RudderStack drops other event types for this destination.

Connection

Identify behavior

Per-source keys

Both keys are objects keyed by the local source type — the tokens listed under Source types. A key naming a source type this destination doesn’t support fails validation.

connection_mode:
  web: cloud
  cloud: cloud

Source types

Attentive Tag accepts events from these source types in the mentioned connection modes:

Every source type is cloud only — events reach Attentive from RudderStack’s servers, never in device mode.

The dashboard additionally offers Attentive Tag to AMP, Shopify, and Reverse ETL sources. Rudder CLI doesn’t manage those connections, so amp, shopify, and warehouse are invalid here.

Connect a source

An event stream connection to this destination is checked against two rules at validate time.

The source’s type must be supported. A source’s type resolves to one of the tokens above before the check — a JavaScript source resolves to web, and webhook and server-side SDK sources resolve to cloud. An unsupported type reports:

destination 'attentive-prod' (type 'attentive_tag') does not support source 'my-source':
source type 'amp' is not among supported source types: android, android_kotlin, ...

The destination config must carry a connection_mode entry for that source type. This lives on the destination spec, not on the connection spec. Without it:

destination 'attentive-prod' config has no 'connection_mode' entry for source type 'web'

Attentive Tag needs no additional config keys to connect a source of any type.

Secrets

api_key is the only secret key. Write it as a {{ .VAR }} reference and supply the value at apply time:

config:
  api_key: "{{ .ATTENTIVE_API_KEY }}"

export RUDDER_ATTENTIVE_API_KEY="..."
rudder-cli apply

# or
rudder-cli apply --var-file secrets.vars.yaml

Note that:

• The YAML that rudder-cli import writes may or may not include secret keys. Before you apply, make sure every secret key your configuration needs is present and populated through variable substitution.

See How to Use Variable Substitution in Rudder CLI.

See more

• Attentive Tag Destination for where to find the API key and sign-up source ID
• Destination Type Reference for Rudder CLI for the rules shared across destination types
• Destination YAML Reference for the spec envelope