Delivra is a smart email marketing automation platform. It’s easy to use and it allows you to customize your automation strategy. You can develop a strategy that works for your business and that results in converting more leads. Accordingly, Delivra is a sophisticated marketing automation made simple.
Below you'll find detailed information, specifically for Delivra integrations:
Supported Delivra Integrations
In order to use PieSync, you need to have registered accounts with the apps you selected. At this point, you'll need to connect PieSync to these apps so we can fetch the contacts data configuration. You do this for both apps. To authorize Delivra, simply enter your login credentials, the instructions for the other app will appear on screen, or consult them separately on this page.
If you have previously set up a connection with any of these apps, you do not need to go through these steps again, unless you need a different Delivra account.
[IF] Supported Conditions/Filters
[THEN] Supported Actions
Default Field Mapping
Depending on the application you're syncing with, you'll see a number of standard Delivra fields being mapped by default. For instance, in a connection with Salesfore, the default field mapping looks like this:
Customizable Field Mapping
You can custom map your Delivra Custom Fields and any additional standard fields that aren't included in the default mapping yet. Bear in mind a mapping between two fields can only exist if the types of fields are compatible, and the particular compatibility will determine the direction of the mapping as well. More information on Customizable Field Mapping here.
You have the ability to sync back the contact status into your CRM. An easy way to do this would by setting up a direct mapping from the Contact status field into a custom text field over in your other app.
There are CRM's that can take in that piece of text that in turn trigger workflows if this is what you need to happen. However, you can also have PieSync directly change certain attributes based on what is happening inside of Delivra. This would require setting up specific filters or actions from the PieSync Rules like so:
Why are the default field mappings not showing my actual fields?
Delivra allows to change any field in the app (except for the Email field). For the fields in the default mapping, PieSync will use the default label. In case you've changed the usage of existing fields, then this could have impact on the sync.
For instance in the below example the First Name field has received a new label which no longer links in any way to the original usage. Still, PieSync will have a default field mapping including the First Name, which in this case will sync the "A Brand New Label" field with the first name field of the other app.
Can I change existing fields to become picklists?
Delivra allows their end users to change every field from a free text field to a Picklist field. Doing so could break your sync and could lead to many contacts being rejected to sync (as the field value in the other app is not one of the picklist options). So we advise to be cautious with this.
The impacts of changing a field to a picklist from a functional point of view can be read in the following document.