> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How allGood connects with your other marketing tools

> An overview of the ways information moves between allGood and your other tools, and how to tell which path a tool will use.

Your marketing data lives in many places: your CRM, your website, webinar platforms, ad platforms, and vendors who send you leads. This article explains the ways those tools connect with allGood, so you know what to expect when you bring a new tool into your stack.

## Why it matters

allGood brings each person's activity together in one place. When a person attends a webinar, downloads a whitepaper, and chats with sales, all three show up on their record. Your motions can then act on the full picture, and Salesforce stays up to date.

That only works if every tool you rely on has a path into allGood. Knowing the paths helps you plan a new tool, or a move from another platform, without gaps in your data.

## The ways tools connect

### Salesforce

Salesforce is the foundation. allGood syncs people, companies, and campaign membership with Salesforce in both directions. Most of what allGood does ends up reflected in Salesforce, so your sales team sees it where they already work.

Salesforce is also a path in its own right. Many vendors can only deliver to a short list of named platforms, and Salesforce is almost always on that list. When a vendor sends leads to Salesforce, they reach allGood through the Salesforce sync.

### Your data warehouse

allGood can share data with your Snowflake account, and read data from it. If your team already keeps data in Snowflake, allGood can use it without anyone exporting files.

Some vendors deliver straight into Snowflake. Intentsify, for example, integrates directly with Snowflake. If a vendor offers Snowflake delivery, that's another way to get its data into allGood.

### Your website

The allGood tag and allGood forms run on your website. Together they record page views and form fills, and tie them to the right person. If you're coming from Marketo, this replaces the Munchkin tracking code and Marketo forms.

### Tools that send information to allGood

Many tools can send activity to allGood as it happens. Webinar platforms, content platforms, interactive demo tools, and ad platforms with lead forms often work this way. Some send the moment something happens. Others send every few minutes or once an hour.

A few tools work the other way around: allGood checks them on a regular schedule and picks up anything new. The result is the same either way. The activity appears on the person's record.

For more on how incoming information works, see [Understanding incoming and outgoing webhooks](https://docs.allgoodhq.com/mk/integrations/webhooks.md).

### allGood sends information to other tools

allGood can also send a person's details to another tool when something happens. For example, it can send a new person to an enrichment service. It can open a ticket in your help desk, or post a Slack alert for sales.

### File uploads

Some information arrives as a spreadsheet. Event attendee lists and leads from content syndication vendors are common examples. You upload the CSV or Excel file, and allGood matches each row to a person and records the activity.

### Tools without a ready-made connection

If a tool has an API, your allGood team can often build a custom connection for it, even when allGood doesn't have a ready-made integration. Ask your team whether a tool you use is a good fit.

## Which path a tool will use

When you evaluate a new tool or vendor, ask them these questions, in this order:

1. **Can you deliver to Salesforce, or to Snowflake?** If yes, the tool's data reaches allGood through that connection.
2. **Can you send data to a web address (URL) that we give you?** If yes, allGood can receive it directly.
3. **Do you have an API?** If yes, your allGood team may be able to build a custom connection.
4. **Can you export a file?** Almost every tool can. A file upload is the fallback that always works.

If a tool can do more than one, your allGood team will help you pick. The best path gives you fresh data with little upkeep.

## What to expect

**Timing varies by path.** Information from your website and from tools that send as things happen arrives within minutes. Scheduled checks and syncs can take up to an hour. File uploads arrive whenever someone uploads the file.

**Fields have to be matched.** Every tool names its fields differently. One tool's *Job Title* might be another's *Title*. Part of connecting a tool is matching its fields to yours, so information lands in the right place.

**Your allGood team sets up connections.** Tell your team which tool you want to connect and what should happen when its data arrives. They'll confirm the path and handle the setup.

## If you're coming from Marketo

Each type of Marketo connection has an equivalent path in allGood:

| In Marketo | In allGood |
| - | - |
| Salesforce sync | Salesforce sync |
| Munchkin tracking code and Marketo forms | The allGood tag and allGood forms |
| LaunchPoint services, and vendors that write into Marketo with their own API access | Tools that send information to allGood, or delivery through Salesforce or Snowflake |
| **Call Webhook** flow steps in Smart Campaigns | allGood sends information to other tools |
| List imports | File uploads |

Before you switch a Marketo connection off, check that its replacement path is working, so no leads or activity are missed.

## Get help

If you're not sure how a tool should connect, contact your allGood team. Include the tool's name, what data it has, and what you want to happen when that data arrives. If the tool's vendor has documentation about its delivery options, send that too.

## Related articles

* [Understanding incoming and outgoing webhooks](https://docs.allgoodhq.com/mk/integrations/webhooks.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.