The following article details best practices and FAQs for leveraging data from your BrightTALK webinars and videos through the POST Connector. For platform-specific information on getting your connector setup, please see this page.
Will this Connector work with my Marketing Automation/CRM System?
Since the POST Connector is not platform specific, there's a good chance that we can still integrate with your preferred system even if it isn't listed here.
To be able to accept a POST, your system must:
1) Be able to provide an HTTP (or HTTPS) POST URL for us to send leads to. This is often achieved by creating a web form (or web to lead form).
2) Accept the parameters as URL Encoded ("form-urlencoded"). JSON and XML are not supported through this Connector.
3) Allow us to deduplicate by Email. We do not currently support any other method of deduplication.
What is a POST URL?
In this particular instance, a POST URL is a method for BrightTALK to send data to your system without directly accessing it. Since we don't have access to your system, we don't require or store sensitive information like API Keys, Secrets, or User passwords.
What is the difference between sending parameters as "Part of the Body" or "Part of the URL"?
Depending on what system you are using, the parameters (i.e. the fields and values we are sending) may need to be sent as "Part of the URL" or "Part of the Body." Here are examples of both:
Parameters as part of the URL:
Parameters as part of the Body:
url = http://api.vendor.com/post/fd539390-5d81-47d9-9461-b19fd58346e7
urlencode = application/x-www-form-urlencoded
body = Email1firstname.lastname@example.org&FName=John&LName=Smith
What are Custom Value Fields?
Custom Value Fields are hard-coded fields that you can include in your sync. For instance, if you have a field called "Lead Source" and you need every lead BrightTALK sends to include that field with the custom value "BrightTALK," you can set that up like this: