Talon.One

Using the Talon.One Integration

The Talon.One integration allows SmarterSends users to add personalized coupon codes from running Talon.One campaigns to marketing messages.

Campaign creators select an approved Talon.One campaign, and a recipient-specific coupon code is requested when the message is delivered.

Availability

The integration is available when Talon.One has been enabled for your SmarterSends account.

Different parts of the workflow require different access:

• Account owners configure or remove the integration.
• Template managers configure Talon.One Offer content areas.
• Campaign creators select offers and expiration dates.

Integration Requirements

Before connecting Talon.One, confirm that you have:

• A Talon.One deployment.
• A Talon.One Application.
• At least one running campaign with the Coupons feature enabled.
• The Application ID.
• A Talon.One Management API key that can access the Application’s campaigns.
• A supported messaging-platform configuration for generating coupons during delivery.

The Management API key entered in SmarterSends is used to retrieve campaign information. The credential used to generate recipient coupons during delivery is configured separately in your messaging platform.

Connecting Talon.One

Account owners can configure the integration:

1. Open Settings.
2. Select Integrations.
3. Select Talon.One.
4. Enter the Deployment URL.
5. Enter the Application ID.
6. Enter the Management API Key.
7. Select Test API Access.

When the connection succeeds, SmarterSends displays API Access Successful and shows how many running coupon campaigns were found.

Deployment URL

Enter the base domain for your Talon.One deployment.

Example:

company.europe-west1.talon.one

You can enter the domain without https://. SmarterSends uses a secure HTTPS connection automatically.

Application ID

Enter the numeric ID of the Talon.One Application containing the coupon campaigns you want to use.

Only campaigns within this Application are loaded into SmarterSends.

Management API Key

Enter a Talon.One Management API key with permission to retrieve campaigns for the selected Application.

Store this key securely. If the key expires, is revoked, or loses the required permissions, SmarterSends will no longer be able to load Talon.One campaigns.

Saving the Integration

After API access is validated:

1. Review the number of running coupon campaigns found.
2. Choose whether campaign creators can set an expiration date.
3. Select Save.

If you change the Deployment URL, Application ID, or Management API Key, test API access again before saving.

Configuring Coupon Delivery Credentials

SmarterSends retrieves campaign information using the Management API key, but recipient coupons are generated through Talon.One’s Braze integration endpoint during delivery.

Your Braze environment must contain a Connected Content authentication credential named:

talonone-connected-content

Configure that credential using a Talon.One third-party API key created for Braze. Do not place the API key directly in campaign HTML.

The Braze user identifier used during delivery must correspond to the customer integration ID used by Talon.One. If these identifiers do not match, coupon generation or customer association may fail.

For the external credential setup, see Talon.One’s Create coupons via Braze guide.

Available Talon.One Campaigns

SmarterSends loads Talon.One campaigns that:

• Belong to the configured Application.
• Are currently running.
• Have the Coupons feature enabled.

Campaign changes can take approximately 15 minutes to appear because campaign data is temporarily cached.

If a campaign is missing, confirm its state and features in Talon.One.

Configuring a Talon.One Offer Content Area

A template manager must add a Talon.One Offer content area to a template before campaign creators can select coupon campaigns.

1. Open Templates.
2. Create or edit a template.
3. Add a content area.
4. Select Talon.One Offer as the content-area type.
5. Select the eligible Talon.One campaigns.
6. Configure the offer HTML.
7. Save and publish the template.

The eligible-offer setting can allow:

• All running Talon.One coupon campaigns.
• Only selected coupon campaigns.

Selecting All Offers allows the template to use any eligible campaign returned by the integration. Selecting individual offers limits campaign creators to that approved list.

Formatting Coupon Content

The Talon.One Offer content area supports the following fields:

• result.Value
• talon_one.campaign_name
• talon_one.campaign_id
• talon_one.expires_at

Use these fields to control how coupon information appears in the message.

result.Value

Displays the recipient’s generated coupon code.

The capital V in Value is required. Use the provided merge-tag control to avoid entering the field incorrectly.

talon_one.campaign_name

Displays the name of the selected Talon.One campaign.

talon_one.campaign_id

Displays the numeric ID of the selected Talon.One campaign.

talon_one.expires_at

Displays the expiration date selected by the campaign creator. The default display format is abbreviated month, day, and year.

Selecting an Offer in a Campaign

When a campaign uses a template containing a Talon.One Offer content area:

1. Open the campaign.
2. Locate the Talon.One Offer section.
3. Select an offer.
4. Select an expiration date when required.
5. Continue reviewing and scheduling the campaign.

The offer list is limited by the template’s eligible-offer settings.

Expiration Dates

If expiration-date selection is enabled, the campaign creator must choose a date before the campaign can be scheduled.

Dates before the current date cannot be selected.

The selected expiration date is sent to Talon.One as the end of that day in UTC. Confirm that the date is consistent with:

• The Talon.One campaign’s schedule.
• Promotion terms and conditions.
• Coupon redemption rules.
• The marketing campaign’s delivery schedule.

If expiration-date selection is disabled, SmarterSends does not include a custom coupon expiration date in the delivery request.

Removing an Offer

To clear a Talon.One selection:

1. Locate the Talon.One Offer section.
2. Select Remove Offer.

This removes the selected Talon.One campaign and expiration date from that content area.

Previewing Talon.One Content

During preview, SmarterSends retrieves the selected campaign’s information from Talon.One and places it into the configured HTML.

The preview displays:

• The Talon.One campaign name.
• The campaign ID, when included in the template.
• The selected expiration date.
• SAMPLECODE in place of a real coupon.

SAMPLECODE is used only for preview. SmarterSends does not create a real Talon.One coupon while rendering the standard campaign preview.

Generating Coupons During Delivery

When the campaign is prepared for delivery, SmarterSends inserts a Connected Content request into the message.

The request contains:

• Talon.One deployment URL.
• Talon.One Application ID.
• Selected Talon.One campaign ID.
• A message dispatch identifier.
• The recipient’s integration identifier.
• The selected expiration date, when applicable.

During message delivery, the messaging platform sends the request to Talon.One. Talon.One generates or returns the coupon code, and the value is inserted wherever result.Value appears in the message.

Coupon format, redemption limits, budgets, and other promotional rules remain controlled by the selected Talon.One campaign.

Supported Message Types

Talon.One Offer content areas can be used in supported templates for channels such as:

• Email
• SMS
• Push notifications
• In-app messages

Actual availability depends on your messaging-platform configuration and the templates published for each channel.

Testing the Integration

Before using the integration in production:

1. Confirm that API Access Successful appears in SmarterSends.
2. Confirm that the intended Talon.One campaign appears in the eligible-offer list.
3. Create a test campaign using a Talon.One-enabled template.
4. Select an offer and expiration date.
5. Confirm the standard preview shows the campaign name and SAMPLECODE.
6. Send a test through the connected messaging platform using a valid test recipient.
7. Confirm that an actual coupon code replaces result.Value.
8. Verify the new coupon in Talon.One.

A standard SmarterSends preview cannot verify live coupon generation because it intentionally uses SAMPLECODE.

Removing the Integration

Account owners can remove the connection:

1. Open Settings.
2. Select Integrations.
3. Open Talon.One.
4. Select Remove Integration.

Removing the integration clears the Talon.One settings from SmarterSends. It does not delete Applications, campaigns, or coupons from Talon.One.

After removal:

• Talon.One campaigns can no longer be loaded.
• Talon.One Offer content areas cannot be configured successfully.
• Campaigns using Talon.One content may fail validation or delivery preparation.

Troubleshooting

API Access Failed

Confirm the Deployment URL, Application ID, and Management API Key. Verify that the key is active and has access to the selected Application’s campaigns.

No coupon campaigns were found

Confirm that the Talon.One campaigns are running and have the Coupons feature enabled. Also verify that they belong to the configured Application.

A recently updated campaign is missing

Allow approximately 15 minutes for the campaign list to refresh.

The expiration date is required

Your organization allows campaign creators to set coupon expiration dates and requires a date for the selected offer.

The preview shows SAMPLECODE

This is expected. A real coupon is requested only during message delivery.

The delivered message does not contain a coupon

Confirm that:

• The talonone-connected-content credential exists in the messaging platform.
• The third-party API key is valid.
• The selected Talon.One campaign is still running.
• The campaign has the Coupons feature enabled.
• The recipient identifier maps correctly to the Talon.One integration ID.
• The template uses result.Value with a capital V.
• Delivery rate limits do not exceed the integration’s capacity.

An offer is available in Talon.One but not in the template

Confirm that the template permits All Offers or explicitly includes that campaign.

Protecting Credentials

Treat both the Management API key and the third-party coupon-generation key as sensitive credentials.

• Do not place keys directly in campaign content.
• Limit each key to the access it requires.
• Monitor expiration dates.
• Rotate keys according to your organization’s security policy.
• Test the integration again after replacing a key.