Avoid triggering export

When changes are made to your contacts (by updating, adding or deleting them) through a file import or the bulk API, some exports will be automatically triggered in Customer Engagement. If you don’t want this to happen, you can use the attribute avoidTriggeringExport. Setting this to “true” will suppress both the automatic BI and contact XML exports.

The default for avoidTriggeringExport is “false” which means that BI and contact XML exports will be triggered by changes made to your contacts. You will only need to include it (as “true”) if you don’t want these BI and contact XML exports to be triggered.

The avoidTriggeringExport attribute only suppresses the automatic BI and contact XML exports. Webhooks are not affected and will still be triggered by changes made to your contacts.

This setting was previously known as “silent export”.

For XML

For an XML import, avoidTriggeringExport is handled as an attribute in the top-level <contacts> node:

<?xml version="1.0" encoding="utf-8"?>
<contacts xmlns="http://eClub.Schemas.ImportContact" avoidTriggeringExport="true">
    <new>
        <member>
            <contactId>20b86e7c-bbeb-46a8-a6fb-0af261aa7534<contactId/>
            <infobaleenEmailCampaign>True<infobaleenEmailCampaign/>
	    </member>
    </new>
</contacts>

For bulk API

When using the contact bulk API, avoidTriggeringExport is passed in the query string:

PATCH /api/v3/contacts/bulk?avoidTriggeringExport=true&contactType=Contact

Constraints

Suppressing automatic exports with avoidTriggeringExport set to “true” in your XML will only work if inside the contact type block (“member” in the example above) you only have custom attributes and the identifier (such as contactId).

If, apart from the identifier, your XML contains even one standard contact attribute when avoidTriggeringExport is set to “true” then your import fails and an error will be written to the integration log.

See the standard contact fields list

If an import is done with only keys and standard contact attributes, but avoidTriggeringExport is false or missing, exports will then be triggered as normal and entries added to “changelog” and “lastmodified”.

The avoidTriggeringExport flag can’t be combined with either of the ImportSettings InsertNewContacts and ShouldDefaultSetIsApprovedAsTrue.

Importing historical data

Data import by file

Data export by file

Avoid triggering export

For XML

For bulk API

Constraints

See the standard contact fields list

​For XML

​For bulk API

​Constraints

See the standard contact fields list

For XML

For bulk API

Constraints