Skip to main content
Avina creates a record in the Avina Signals custom object (AvinaSignals__c) in your Salesforce org each time an audience finds a lead you’ve chosen to push. The object stores each lead’s activity in a structured format you can use for reporting, automation, and workflows.
Each record contains:
Example record (what you’ll see in your Salesforce org):
Signal Summary: Avina Alert: Dev Security hired Brandon Riley as their new Chief Revenue Officer. He joined the company in Feb 2025 and is based in Ann Arbor, Michigan, United States.
Tags: avina_new_hire_signal

Setup Guide

Before Avina can push audience activity to your Salesforce org, you need to create the Avina Signals custom object that stores it.

Creating the Custom Object

  1. Download the object definition: Download CSV file that defines the custom object attributes.
  2. Navigate to Object Manager: In your Salesforce org, go to Setup → Object Manager.
  3. Create Object from Spreadsheet: Click Create and then select Create Object from Spreadsheet.
  4. Upload the CSV: Upload the downloaded CSV file to create the AvinaSignals__c custom object.
  5. Complete the import: Add the CSV to the import list. If you encounter any issues, try using an incognito/private browser window.
  6. Find your new object: Go back to Object Manager and locate your newly created Avina Signals object.
  7. Create Account lookup field: Click into the Avina Signals object, then click New to create a new field. Select Lookup as the field type, choose Account as the related object, then click Next through the setup process and Save.
Lookup Field Creation Lookup Relation Setup
  1. Create Contact lookup field: Repeat step 7, but this time select Contact as the related object for the lookup field.
  2. (Optional) Create Lead lookup field: Repeat step 7, but this time select Lead as the related object for the lookup field.
  3. Enable push settings for Salesforce: Go to Settings → Integrations in Avina. Select the Salesforce card and, under Preferences, turn on Push resolved contacts to Salesforce and/or Push ICP contacts to Salesforce, then Push audience activity to account and contact records. To push only certain audiences or leads instead, use the Push Audience Match to CRM automation action.
  4. All done! Avina will start creating records in your Avina Signals custom object, linked to the related Account and Contact records, as your audiences find new leads.

Tag reference

Every record carries a tag for the kind of activity, and often a few more. Match with contains rather than equals when you build reports, lists, or workflows. Avina also adds context tags describing the account at that moment: open_deals, closed_won, closed_lost, and has_owner. When a lead was pushed because of an automation, the record also gets a “Triggered automation: name” line and an avina_{automation_name}_automation tag. See CRM Labels.
Tip: An AI Audience’s own tag (for example, avina_funding_round_signal) targets exactly that audience, which makes it the most precise tag to build on.

Triggering automations with Salesforce Flow Builder


Example use-cases


Best practices & FAQs