In this version of the integration, we remove the need for any custom campaign tracking. Before you start, you’ll need to set up a HTTP Authentication integration with Jacquard. Then, you're ready to configure the webhooks and scenarios.

The second Bloomreach integration we need to set up is the Webhook preset. This is the technology that will actually pass your language variants from Jacquard to Bloomreach.

Head back to the Integrations section where we set up the HTTP Authentication. Hover over Webhook preset and click Add integration.

Again, start by giving your integration a unique name. We have used Phrasee Get Variant in the example below.

Now, it's time to complete the settings.

Selecting an Icon is optional, as is adding a Description. (But they both make it all look so much prettier down the road, and who doesn't want that?)

Set the Preset type to Normal Webhook. Set the Endpoint URL to GET. For the URL itself, paste in the below:

In the Jacquard Bloomreach environment, email_id is the customer key. If this is different in your account you’ll need to adjust the URL to reflect that.

For the Authentication method, you can now select the HTTP Authentication integration you created before. You'll recall we named ours Phrasee Realtime for our example.

Your setup should now resemble the below:

Under Response processing, choose Process response as JSON.

You will also have to create a Throughput policy at this point. Toggle the Throughput policy switch on. Then, click the gear that appears.

Your Customer Success representative will have a recommendation for what you should enter here. In our example, we've chosen Realtime API for the Policy name and a Concurrency limit of 35.

The assignment of the Consent category will depend on your Bloomreach setup. Customers is the default here.

Now, click Save integration.

You can now use this Get Variant webhook when deploying your experiments, without the need for any custom campaign tracking attributes. For a guide to deploying your experiments see here for Broadcast and here for Triggers.

But before deploying, first we need to set up your tracking scenarios.