"How does Confection work?"

Demo 1: Forms

Web forms have two problems in privacy-first environments.

First, if a form relies on one or more third-party scripts, that form might not load at all. Confection knows when a browser is preventing a form from rendering. When this happens, our app converts the blocked form into a static, local one. There’s no need to spend time replicating and replacing forms you’ve already created.

The second issue is more common. If a form sends data to a third-party server, that form might fail to send any information when the user clicks “Submit.” Confection works around this by sending all form data to our server in real time.

To see this in action:

1 Select a form from the dropdown menu, and enter some information. (If you see a form, you’re not having the first issue we outline above.) As you enter data, you’ll see it immediately appear in the purple box.

2 After you’ve added some form data, click the “Show API Data” button. In the blue box, you’ll see the JSON structured snippet we use to pass usable data back to our customers. Use this in your CRM, marketing automation solution, programmatic ads, custom app/API, or in 1,000s of apps via Zapier, Pipedream, Integromat, and Tray.io.

Select a FormSalesforceMailChimp

Demo 2: Events

Privacy-first environments also block certain types of engagement activity, parameters, and other browser events, especially if they rely on cookies, custom JavaScript, and third-party servers and scripts. This limits — and, in some cases, completely undermines — the utility of many marquee data services.

Even in the most privacy-forward browsing environments, Confection can work around these limitations. To see this in action:

1 Click any service name. This will send a generic pageview event to that system (middle box) and Confection (top box). Note that, even when the data service fails, Confection is able to write the event to its server.

2 Just like the form demo, if you click the “Show API Data” button in the blue box, you’ll see the JSON structured snippet we use to pass usable data back to our customers. Use this in your CRM, marketing automation solution, programmatic ads, custom app/API, or in 1,000s of apps via Zapier, Pipedream, Integromat, and Tray.io.

Note, the events array object value may be blank, eg: "value": "" Confection is not malfunctioning. Returning an event value is optional, and the demo does not do so by default.

Click to Load More Services

Demo 3: Unified UUIDs

Curious about your own data? Click the “Show API Data” button in the blue box. You’ll see a JSON structured snippet that contains the data you’ve sent to Confection.

If this is your first session, you’ll see information associated with a single UUID. If this is your second+ session — if you’ve visited this page before, refreshed it, or visited another site where Confection is installed within 24 hours* — you’ll see a list of UUIDs at the bottom of the API output. (See the related object.) Behind the scenes, Confection uses a blend of predictive algorithms and AI to link UUIDs that have similar traits, assign them probable “likeness” scores of 1-99%, and consolidate them into single user records. No need to worry about persistent front-end browser, user, or device IDs.

Using your account API, you can retrieve the full details of these related UUIDs to build cross-session intelligence on users. Just like the demos above, use the information you collect in your CRM, marketing automation solution, programmatic ads, custom app/API, or in 1,000s of apps via Zapier, Pipedream, Integromat, and Tray.io.

Note, the Confection demo doesn’t retrieve all fields and event data for all related UUIDs. What you see is just a sample of what’s available, specifically, email addresses (if available) and scores. Displaying the full set of data to all demo users all the time would create unnecessary performance demands and increase costs. This seems unnecessary given that 90% of this demo data is disposable. Users with accounts can query the Confection API to return all data for a specific UUID.

* By default, Confection stores data for 24 hours. Most customers write data in real time to a meaningful endpoint (eg., Google Analytics or a CRM). As a result, this isn’t an issue for them. However, storing data for > 24 hours would allow you to build extensive sets of related UUIDs with deep historical intelligence about your users and visitors. If you do want to store account data for longer than 24 hours, you have two choices:

Demo 4: Compliance

Confection is compliant with global data privacy laws such as CCPA, GDPR, and LGPD. We offer customers two ways to collect data:

1 Complete Zero- or First-Party Data
We send all data to an endpoint the customer defines and store no personally identifying information (PII) inside Confection.

2 Full Service
Customers offload total compliance — collection, storage, and distribution — to us. We manage PII data for them, and customers can access it whenever they need it.

No matter which option they choose, all customers have the option to collect, store, and distribute data in accordance with the data protection law of their choice. Each video (below) illustrates one of Confection’s three current options: no compliance/consent (which assumes a user is gaining consent using a different method), CCPA and GDPR compliance, and LGPD compliance.

In addition to helping our customers stay compliant, Confection’s approach is an improvement over generic, all-or-nothing cookie banners.

Businesses
Even if a user opts out of PII collection, continue collecting compliant, anonymous data in a way that’s unaffected by client-side disruptions. There’s no need to worry about cookies, cross-domain scripts, or device IDs.

Users
Opt in and out of data collecting as you see fit. Understand what kinds of information a site is collecting when it starts collecting it. Take action in the moment, fine-tune settings on a site-by-site basis, toggle data sharing as desired, and write all data to — and manage all data using — a single, centralized repository.