This article explains how the various integrations work between Envoke and third party software.
Export / import lists manually
There are several reasons why you may want to manually export / import contacts before implementing an automatic sync of databases
No need to involved your IT team / developers
You're just starting out and want to be sure Envoke works well for you before committing to an implementation project (which takes up IT time on your end)
You're sending emails infrequently and the overhead to export/import contacts isn't significant. For example, a manual import/export process once a month may be a better solution than setting up automated list syncing.
Manually exporting/importing contacts before sending email blasts takes approximately 30 minutes in most cases.
During the import duplicates are automatically merged
Consent status is preserved. You can't accidentally re-subscribe contacts who had previously unsubscribed.
Add contacts from your CRM system to Envoke
Adding and updating contacts from your CRM system to Envoke ensures that the Envoke database is always up to date, which in turn allows you to send targeted and relevant messages to your contacts at any time.
Using the APIs
This integration needs to be implemented by your developers using the Envoke contact APIs with the help of documentation and examples provided by Envoke. You can also book a developer-to-developer call to review API setup requirements. Please visit this page to get started with API integrations.
Access to the APIs is available at no extra cost with the Professional, Multi-account and Pay As You Go Plans. See billing plan details.
Uploading a contact list file to Envoke daily
This option works well if you can automatically produce a CSV file of contacts and upload it to Envoke daily. It also needs to be implemented by your developers. With this option the list file you upload to Envoke is processed overnight every day. New contacts are added, existing contacts are updated and contacts that don't exist in the latest list file are removed.
This approach ensures your database is up to date on a daily basis. If you can't automatically extract and upload a CSV file to Envoke then you should use the APIs.
This daily list upload is available with the Professional, Multi-account and Pay As You Go Plans: It's free for the first account and costs $100/mo for subsequent accounts. Contact Envoke support to learn more and for technical requirements.
Update your CRM system when contact data changes in Envoke
You can use a special type of API called "web hooks" to receive data from Envoke when contacts are created and updated. Read technical details to set up web hooks.
Sample use case: When a contact unsubscribes in Envoke their subscription status is updated in your CRM. When a contact updates their own contact profile (for example phone number, etc) this data is updated in your CRM.
By connecting to Zapier you can update changes from a CRM system to Envoke.
Implementation is done by your IT team, including business logic for API triggers. A Zapier account is required.
Limitations of using Zapier:
Customers cannot use Zapier if data storage in Canada is a requirement.
Zapier support for CRM systems is limited to more popular CRM platforms such as Salesforce. The Envoke contact APIs make it possible to create integrations with any CRM.
Bidirectional integration (sending Envoke data to your CRM) is not currently possible. You can only send data from your CRM to Envoke using Zapier. You can use webhooks to pass data from Envoke to your CRM system.
Track email activity on your website using Google Analytics. Read more.
Use case: Links in emails are tagged with UTM tags, which allows you to track email traffic in Google Analytics: https://yourdomain.com/page?utm_campaign=may_newsletter
A data warehouse is available for a fee. Use it to create custom queries for aggregate email activity. All PII is removed. The data warehouse can be used together with Microsoft Power BI, Google Data Studio or other analytics software to create custom reporting dashboards.
Use case: Email opens/clicks over time, email opens/clicks by time of day, compare email campaign performance.