Measure beyond engagement metrics to track conversions
Jacquard now offers a capability to show which messages drove conversions on your website so your reporting can examine commercial outcomes beyond campaign engagement metrics. Reporting can attribute purchases, basket additions, signups, form completions, or any event you care to track back to the campaign that delivered them. Once configured, per-campaign revenue reporting lands in your Jacquard account, updated daily.
Setup is simple: We will work with you to add our tracking snippet to your site, identify visitors with the same ID your customer engagement platform (CEP) uses, and fire an event when a conversion happens. Attribution is configurable across the models and lookback windows common to modern CEPs (i.e. last-touch, first-touch, and click-only, with windows from 1 to 30 days) so it lines up cleanly with how you're already measuring campaigns.
We're releasing the same capability as a Google Tag Manager tag shortly so your marketing team can enable it without a code deployment. Support for other surfaces is on the way soon.
Speak with your Jacquard Customer Success representative to get started.
Faster language generation
Making the Jacquard platform faster to get to great on-brand language continues to be an area of focus. This week we introduced some further improvements which have cut generation times by around 30%. Most of the time, this means our 9 separate agents are running end to end across hundreds of variants and returning in about 60 seconds. We’re continuing to identify and implement improvements in this area in the coming weeks.
Replace function now adapts to user feedback (and it’s faster)
When users reject language and give a reason, Jacquard now generates new variants taking the feedback into account and generates the replacement about twice as fast as before.
You can now shape replacement variants instantly through your feedback. Use the "Please tell us why" feedback box to guide how each new variant is generated - your input steers the new content, and variants stay diverse and distinct from one another. This gives you more control over the replacements you receive. You can use the feedback to:
Include additional content or themes, for example:
include father’s day and free shipping
talk about cruelty free cosmetics, not beauty
Remove content or themes, such as:
don’t talk about health
cheap is off-brand for us
Shifts in tone, such as:
make it more engaging
less urgency
Note: If the feedback conflicts with the user-provided brief, the model does not make decisions about which takes precedence
Variant-level user feedback influence exclusions
While the theme, content, and tone feedback is robust, variant-level user feedback cannot currently influence other aspects of the variants such as:
length
emoji allocation
stylistics
Additionally, users should make specific punctuation changes (e.g. adding a period, removing a comma) by editing the variant directly.
Fragment-level language settings
Previously, language settings applied to all parts of multi-fragment content (e.g. email subject line/preheader, push message title/body). Now, each fragment can have its own independent settings.
The following are just a few examples of use cases Jacquard now supports:
Length: The max length of each fragment can be set independently
Emoji configurations (left side, right side, or both): Emoji assignment is now handled based on the fragment text only, not the entire variant, ensuring greater relevance. (e.g. A restaurant won’t get a 🍰 emoji in a subject line mentioning dinner just because the preheader included the word dessert.)
Punctuation: Punctuation settings can vary by fragment. (e.g. A user wants full stops on preheaders but not on subject lines.)
Capitalisation: Fragments can be set to title case and sentence case independently. (e.g. Push titles or email subject lines can be set to title case while the push body or email preheader remain in sentence case.)
Users can raise a support ticket to request these individual fragment configurations. Please note the impacted account, brand voice, and content types in your ticket description.