...
Using CRM segments to help integrate with an external CRM
Some clients may prefer to segment their supporters or create mailing lists in their external CRM (rather than Engaging Networks). CRM segments allow for the list to be created in a CRM and then imported into Engaging Networks via the bulk import API. Then that segment can be targeted with a broadcast campaign.
When importing supporter data, the supporters in a particular batch can be associated with an external CRM segment by submitting the segment parameters segmentId and segmentName as part of your form post.
...
For example: I have 20,000 supporters imported from a segment called “2014-07-01-SEGMENT”. Here I would include that name in my import as “segmentName”. This would later allow me to select all supporters who formed part of that import.
In the The following video , Ben Childers, Director of Account Services walks will walk you through using the External CRM Segment tools.
...
Any supporter you’re importing transactional data for needs to already have an existing constituent record in the database. If they don’t exist, you’ll need to create them via lookup supporters or by supporter data import. You can reference them with either their email address or their supporter ID.
You must know a private token key for the subaccount. If you do not have a private token, log into the admin dashboard for your subaccount and navigate to Hello Your name > Account settings > Tokens. Here you can either check your private key if one already exists, or generate a new one. One private key can be generated for each dashboard user. Import jobs created via the API will be assigned to the user associated the private token used to invoke the API, and will be visible in the jobs monitor in the corresponding user dashboard.
Your import file must be formatted in a standard way, as defined in the Transactional Data Import Template spreadsheet (see attachment at bottom of the page). Each upload file should only contain rows for a single campaign ID. If you want to import data for several campaigns, this needs to be done in separate files.
The campaign ID column in the import file needs to be the numerical ID of the campaign in the Engaging Networks system. For example, for an advocacy campaign, the ID is the ea.campaign.id parameter that appears in the bottom of the source code of your advocacy page. You therefore will need to have a pre-created campaign in the Engaging Networks dashboard with which to associate the imported transactions.
At the bottom of the page source you will see:
<!– Page Name:[page id]:[campaign id]:[client id] –>
...