Server Side Pixel Infrastructure

August 07, 2024

Introducing Blotout Edgetag Infrastructure as a Service

Now that we have been well received on Shopify, and have multiple embedded partners who rely on our Pixel for API delivery, we have decided to expand a common D2C Server Side Platform that enables any [ future or current ] partner to deploy its server side pixel [ plus client side code ] using Blotout infrastructure.

What's the big deal?

  1. Deploy your own server side infrastructure without having to rewrite or redeploy code
  2. Upgrade existing tag option to just having a server-side feed
  3. OR Just use pre-existing standard events from Blotout [ zero code ]
  4. Infrastructure as an API [https://swagger.edgetag.io]

Paid Traffic

*Magento = Q3, 2023

Key Features

  1. All platforms are supported and are zero code.

    a. Option to use your tag

    b. Option to use our tagless support

  2. Unified event system - https://app.edgetag.io/docs/standard-events

  3. Zero Code everything [ no tag codebase ]

    a. Closed source codebase for building white label tools

    b. Just use Blotout pre-built apps

  4. Deploy and Manage infrastructure via your existing application

  5. Option to self host application [ or allow us to manage ]

  6. Real time [ Data is delivering within seconds and is geo IP policed and triggered ]

  7. Consent plug-in built in to interpret consent mode

  8. No need for apps in various app stores [ reduce payment rail friction ]

  9. CDP as a service

    a. Meta C-API [ + TT, Google Ads ]

    b. GA4 plug-in

    c. Mid funnel event streams [ Klaviyo, etc ]

    d. 50 to choose from

    e. Stream to your WH or build a zero code lake [ stitched ]

Infrastructure Deployment

  1. Self Hosted [ preferred ]
  2. Managed

Architecture

Paid Traffic

  1. Site SDK is a zero code tag;

    a. Shopify via Web Pixels

    b. WooCommerce via Wordpress plug-in

    c. Etc.

  2. Streaming is edge based (1600 edges via Cloudflare)

    a. Manages server-side ID

    b. Manages consent mapped to long lived server-side ID

    c. Transforms data to 50+ channels [ zero code ] and learnings from 1k+ merchants

  3. Cloud stack

    a. Terraform [ you host, we host ]

    b. M-tenant : zero code map from streaming edge service

    c. 50+ pre-canned models [ DBT based ]

Why work with Blotout?

Blotout infrastructure just scales and allows you to focus on creating value with your application vs. worrying about “what Google or Apple '' are going to do next. So instead of fixating on “trying to hire a team” to work on internet cookie deprecation and consent, focus on building the top application and just use Blotout as a clickstream that does the heavy lifting bringing “event + audience” to you, all zero code.

Finally; there are zero players that support every D2C platform allowing you to scale your reach to Salesforce, Magento, and other platforms that are not called Shopify and enabling scale very quickly.

Why not build this?

The idea for build vs. buy is mostly specific to customers who are looking to move quickly and get a ton of functionality that takes them years.

Buy (License / White Label) Build
Ready to go Live (2 weeks max) Likely takes 6 months to Alpha
Battle tested - 500+ merchants embedded Start at zero
No upfront cost Needs a team of 4-6 to get started
Experienced team who knows how to navigate the internet Build the team
Every D2C platform supported Likely takes 1-2 years of expertise
No cost of maintenance Need to keep 4 engineers handy
Complete CDP functionality 2+ years of dev
Custom Event support 2+ years of dev

We feel strongly [ and you don’t have to agree ] that a SaaS company should build differentiating features and license commodities.

Who should reach out to Blotout?

If you are a SaaS company that needs help with;

  1. ID management
  2. Consent Mode hooks
  3. SS Pixel API feeds
  4. Client and Server side synchronized fires

And critically all of the above with;

  1. Zero code management
  2. 2 KB payloads
  3. Modern SDK that already works in non standard environments (Shopify, SFCC, Wordpress)

Why are we opening this up to everyone?

We realize;

  1. Server side pixels are going to be very common and every SaaS company is going to require this
  2. SaaS companies don’t scale beyond Shopify due to the complexity of other platforms - we just removed those limitations
  3. Install and setup time eats in to a lot of ROI - zero code and 30 minutes
  4. Finally, merchants are going to have 1 ID structure and we, as Blotout, want to power that infrastructure

Paid Traffic

However, beyond the obvious, we also realize that we, as a collective software provider group, need to reduce the redundancy that drives cost for each of us. With one common infrastructure, we have a chance to reduce the cost for merchants to each of us driving better margins across the board.

So is Blotout SS Pixel available as a White Label?

Yes; that's the whole point.

Would we be competing?

Unlikely. But we can provide a POV on how a common customer works. Our infrastructure already supports the ability to run two parallel infrastructures so no harm or foul done.

Would you be able to share use cases?

Yes. However, most of our partners are white label and w/o an MNDA we are unable to share case studies for their successful deployments. We already have 400 merchants that are running on about half a dozen white label deployments.

Where should you reach out?

Talk to us. We are at infrastructure@blotout.io