Data Relationships - Views

Feature Overview

Data Relationships is a Claravine platform capability that allows admins to formally connect separate templates based on shared field values. It reflects the way marketing data is actually structured, where Campaigns contain Ad Sets, which contain Ads, and makes that hierarchy visible and usable inside Claravine.

Before Data Relationships, teams had no native way to link templates. Common workarounds like powered lists created fragmented exports and disconnected workflows. Data Relationships replaces those workarounds with a structured, configurable solution built into the platform.

Data Relationships enables your team to:

• Navigate faster. Jump between related templates (for example, from a Campaign to its Ad Sets) without leaving the page.
• Export smarter. Pull specified data from multiple related templates into a single unified file, rather than stitching exports together manually.
• Work with your actual data structure. Model your campaign hierarchy inside Claravine the way it exists in your ad platforms.
• Reduce manual effort. Eliminate the need to cross-reference separate exports or maintain fragile workarounds to associate datasets.

Data Relationships is available to all Claravine customers. Contact your Claravine admin or account team to have the feature enabled for your account.

How It Works

Data Relationships has two core components: Template Relationships and Views.

Template Relationships are the foundation. An admin connects two templates by adding a relationship between a shared field between them, typically an ID field. For example, a Campaign ID field in an Ad Set template maps to the Campaign ID in a Campaign template. This creates a parent-child link. Lower-level templates point up to their parent; the top-level template does not map upward.

Views are the user-facing experience built on top of those relationships. A View is an admin-configured grouping of 2 to 8 related templates. Users can not only navigate between templates in a View and see them as a unified structure, but also export all related data from the View together in a single file.

How to Use Data Relationships

• For Admins: Planning Your Data Relationships

  Before configuring anything in the platform, take time to map out your template structure on paper or in a simple doc. The setup process moves faster and produces cleaner results when you have a clear picture of your hierarchy before you start.

  Ask yourself these questions:

  • Which templates belong together as a logical group?
  • What is the natural order of those templates? For example, does a Campaign contain Ad Sets, which contain Ads?
  • Which template sits at the top of the hierarchy? That is your parent template.
  • Which templates sit below it and depend on it for context? Those are your child templates.
  • What field do those templates share? That shared field, typically an ID, is what you will use to connect them.

   

• For Admins: Setting Up Template Relationships

  1. In the Template menu, open the child template (e.g. Ad Set template) you want to configure and go to the Define and Govern workflow.
  2. Navigate to the field that is shared with the parent template (e.g. Campaign ID), click the Edit button.
  3. In the Template Relationships section, map a field in the current template to the corresponding field in the Source (parent) template and Source field. (e.g. Campaign template and Campaign ID field)
     
     • Note the Campaign ID field has a Data Relationship icon for easy identification.
       
  4. Save your configuration.

  Repeat this process for each template in your hierarchy that has a parent.

  Best practice: Use an inbound connector to populate the ID fields used for the relationship. IDs are more stable than name fields and more accurately reflect the native structure in your ad platform.

• For Admins: Setting Up a View

  A View groups connected templates into a single navigable unit and lets admins select a subset of fields from each template to surface in a unified export.

  1. In the Structures menu, select Views.
     The Views page displays.
     
  2. In the Views menu, click Create View.
     Begin creating the View.
     
  3. Select Templates: Name the View. Choose a folder, then select the 2 to 8 templates to include in the View.
     • Select your templates in order from most granular to broadest. For example: Ad, then Ad Set, then Campaign.
  4. Configure Fields: All fields from each template appear as designed in their respective template schemas. The Field Name, Type, Template Source, and Visibility information are shown in the table below.
     
     • Drag fields to reorder them as needed.
     • Toggle fields on or off to control which fields from each template appear in the View and its exports.
     • Click Properties to select row-level information per template (such as Claravine ID, Submission Name, Created Date, and user metadata), then click Apply.
       
  5. Set up Outbound Integrations: Configure destinations such as S3, email, or Google Cloud Storage to push View-level data downstream when new data is added to the related templates.
     

• For Users: Navigating within Related Templates and Exporting a View

  Once a View is configured by the admin, you can:

  • Group by View on the dataset landing page to organize your datasets by their relationship structure.
    
  • Use the template switcher to jump between related templates within the same View without leaving the page. The switcher is available in create submission, edit submission, submission details, and all tabs of the specific datasets page.
    
  • Export View from any Dataset to download all related template data in a single file. You can scope the export to all objects in the View, or only objects that have connections from the lowest level of the hierarchy.
    • The export includes only the visible fields designated in the View configuration.
      

Tips and Best Practices

• Use ID fields for relationships, not name fields. IDs are stable and tie directly to how ad platforms structure their data. Name fields can change and may cause mismatches.
• Plan your hierarchy before configuring. Map out your Campaign, Ad Set, and Ad structure in advance so your template relationships are clean and sequential.
• A View supports between 2 and 8 templates. Plan your groupings accordingly.
• Existing template-level integrations are not affected. Platform integrations such as Google Campaign Manager or Meta continue to work exactly as before. Views add a layer on top and do not replace any existing functionality.
• A template can be both a child to one template and a parent to another. For
  example, Ad Set is a child of Campaign and a parent of Ad.
• A template can be used in multiple Views.

Learn More

Continue reading on this topic: Views of Related Data