When you create a forwarding within a campaign, you can either send data to a URL via an API or Forward to another Databowl campaign or even another Databowl campaign on another instance.

You can do this on your campaign, just look out for the forwarding box!

If you are forwarding to an internal Databowl campaign or to another Databowl instance (account) the integration is very simple.

Once you have given the forwarding a name, you simply enter the instance you are posting to, before entering your Campaign ID and Supplier ID.

All the default fields will be pulled through, and then you just need to map your additional fields.

Here's a video to go over the above:

If you select to Forward to a URL, you will see the Forwarding Wizard appear below. Here is a breakdown of the information you will need to provide:

Name: define the name of your URL - this will be visible within the forwarding box in the campaign for reference to help you identify this forwarder.

HTTP Method: please select the relevant method of delivery e.g. GET/POST/PUT

Delivery URL: Enter the URL in which you would like to send the leads to. Additional instructions on adding fields/metadata are shown in the system along with a link to show the available fields you can use.

Set Status - If a response doesn't match any of the responses you have mapped - this will default the lead to Client Rejected. You can change this to any other status - but would recommend you set this to Client Rejected.

Set forwarding Status: If a response fails to match any recorded status - this will determine how Databowl logs the lead. It would be recommended to mark this as Rejected, but you can select another status if needed.

Delay - you can specify a delay from 1 minute to 1 hour on your forwarding. (Note - this will send the lead to the forward queue with a delay - its sent straight away but with a delay of X time).

Weighting - If your campaign has multiple forwarders, you can use weighting to distribute leads to them based on your neeeds.

Then the higher the weighting, the more leads will be distributed towards that forwarding (in proportion to the others).

If you have weighting enabled on one of the forwarders but not on the others, it will be assumed no leads will need to be delivered to this forwarder.

Advanced Settings - if you select this, you will see the following options...

Content type - specify the content type

HTTP Authentication- if applicable you can select either 'Digest' or 'Basic'.
By default it is set to 'None'