Claravine's outbound integrations push governed, validated campaign and asset metadata out of the platform to wherever your team needs it next, whether that's file based destinations like Email, S3, SFTP, and Google Cloud Storage, or media platforms like CM360, Meta, TikTok, and DV360. Once naming and metadata have been validated in Claravine, admins connect a destination once and let that clean data flow out automatically, updating naming conventions directly in a media platform or delivering structured files to a storage location on a set schedule. This removes the manual step of exporting data and re-uploading it elsewhere, cuts down on version mismatches between what's in Claravine and what's live in downstream systems, and gives teams confidence that the data reaching analytics, reporting, or the ad platform itself matches the taxonomy they've already governed upstream.

Outbound Integrations

Keeping naming conventions consistent across systems usually means updating each platform by hand. Outbound integrations remove that manual step, automatically pushing your governed names from Claravine back to the connected platform. An inbound integration must be set up first; any corrected data that is mapped in the outbound integration will write back to the system using the ID as the match value.

Add an Outbound Integration to a Template

To add an outbound integration to a template:

• The integration template must already include the inbound integration configuration.

1. Click + Outbound integrations. 
2. Click the name of the platform's outbound connector. 
   The outbound configuration section for that integration displays.
   
3. Integration Details: Enter the Integration Name. If no value is entered, Claravine defaults the Integration Name to the Template name.
4. Account Selection: Select the connected account from the drop-down list. This should match the data level chosen for the inbound integration configuration.
5. Data Selection: Select which data level to bring into a template. This should match the data level chosen for the inbound integration configuration.
6. Field Mapping: For all data levels, the ID field is required and should be pre-selected. 
   
   1. Click + Add New Mapping to select the field in Claravine to map to the platform's field.
   2. If the account has Claravine AI enabled, click Auto-map Fields to automatically match the fields in your template to the corresponding platform fields, without setting up each mapping manually. Manual mapping is still available if you prefer to map fields individually. 
7. Click Save to save the template.

File-Based Inbound Integrations

Claravine's outbound integrations push governed, validated campaign and asset metadata out of the platform to file-based destinations like Email, S3, SFTP, Google Cloud Storage and others. Once naming and metadata have been validated in Claravine, admins connect a destination once and let that clean data flow out automatically, delivering structured files to a storage location on a set schedule. This removes the manual step of exporting data and re-uploading it elsewhere, reduces version mismatches between what's in Claravine and what's live in downstream systems, and gives teams confidence that the files reaching storage or analytics match the taxonomy they've already governed upstream.

Add an Outbound Integration to a Template

To add an outbound integration to a template:

1. Click + Outbound integrations. 
2. Click the name of the platform's outbound connector. 
   The outbound configuration section for that integration displays.
   
3. Enter the Integration Name. If no value is entered, Claravine defaults the Integration Name to the Template name.
4. Connector-specific folder details are required to import data. Refer to the individual inbound file-based integration articles for each connector's setup requirements.
5. File Configuration. The file configuration options are Custom or Default Summary.
   • Default Summary matches the schema in Define and Govern schema. If the visible box is unchecked in the schema, it will not be included in the file.
   • Custom allows field-specific changes:
     • Include or exclude the field from the file using the checkboxes
     • Change the Output Label/column header
     • Manually drag the tile to change the order
     • Transform menu: Update all Output Labels to:
       • Replace spaces with underscores
       • Replace underscores with spaces
       • Lowercase
       • Uppercase
     • Meta Field menu: Add a new meta field to match file output requirements:
       • Template Name
       • Submission Name
       • Submitter Name
       • Submitter Email
       • Created By
       • Created Date
       • Submission Created Date
       • Updated Date
       • Empty
       • Pattern