Skip to content
Auto Genius Help Center home
Auto Genius Help Center home

Integrations Overview

Overview

Integrations connect your Marketplace site to third-party services that support lead capture, messaging, trade valuations, financing, service scheduling, analytics, and more.

Marketplace integrations typically work through two mechanisms:

  • Project-level configuration flags that enable a feature across your entire site
  • Identity values that store the URLs, IDs, or keys needed to connect a project or location to a specific provider

Auto Genius manages site-level feature enablement. Your team typically provides provider details and, when needed, location-specific values.

Two ways integrations are enabled

1) Project-level config flags

Config flags act as site-wide switches. When a flag is enabled for your project, Marketplace will expose the related experience, such as:

  • Chat widgets
  • Service scheduler options
  • Buy online and other CTA types

Config flags determine whether a feature is available at all.

2) Identity values (project or location)

Identity values store the connection details for an integration, such as:

  • A URL to an external scheduling portal
  • A provider account ID
  • A tracking container ID

Identity values can be set at different levels:

  • Project identities apply site-wide.
  • Location identities apply to a specific rooftop.

This allows a multi-location group to route different locations to different providers without changing code.

How integration routing works in practice

Many Marketplace CTAs are built at render time based on identity values.

A common pattern:

  • If a location has an external integration URL configured for an action, the CTA links externally.
  • If not, the CTA routes to the built-in Marketplace form flow.

This makes it possible to mix external and internal experiences across locations.

What you manage vs what Auto Genius manages

Your team typically provides

  • Which providers you use (trade, chat, service, finance)
  • Provider URLs and account IDs
  • Location-specific routing where needed
  • Any compliance requirements for the experience

Auto Genius typically manages

  • Enabling and validating config flags
  • Implementing and maintaining provider integrations
  • Ensuring the site uses the correct integration on each page type
  • Analytics and event routing configuration
Powered by Plain