# Orkie > Orkie is an AI operations workspace for online businesses. Each business gets a private workspace with installable modules: a first-party pixel with multi-touch attribution, product feeds, ad connectors (Google, Microsoft, Meta, TikTok, LinkedIn, ChatGPT Ads), a CRM, a shared inbox with AI drafts, projects, YouTube/TikTok/Instagram connectors, Shopify and BigCommerce connectors, QuickBooks, Slack and more. Orkie's operators run the work with the client. Owners can talk to their workspace from Claude or ChatGPT through Workspace MCP; anything that messages a customer or changes spend waits for a person's approval. Best for: mid-market ecommerce businesses (roughly $1M to $50M a year) on Shopify or BigCommerce with a lean team and real ad spend, the agencies that run businesses like that, and B2B, service and hospitality businesses that want the same workspace. There is no self-serve signup: the calls to action are a call with us (https://orkie.ai/talk/) and a pixel install request (https://orkie.ai/pixel/). ## Key pages - Home: https://orkie.ai/ - The story (pixel first, then feeds, outbound, scale): https://orkie.ai/story/ - Agencies (a workspace per client): https://orkie.ai/for/agencies/ - What we do: https://orkie.ai/what-we-do/feeds-and-campaigns/, https://orkie.ai/what-we-do/get-found/, https://orkie.ai/what-we-do/email-and-crm/, https://orkie.ai/what-we-do/inbox/, https://orkie.ai/what-we-do/creative-and-video/, https://orkie.ai/what-we-do/related-products/, https://orkie.ai/what-we-do/ai-assistant/, https://orkie.ai/what-we-do/smart-ai-routing/, https://orkie.ai/what-we-do/custom-modules/ - How it works: https://orkie.ai/how-it-works/ - How it works together (the pixel, feeds, related products, CRM audiences, the Outbox and the company brain on one set of data): https://orkie.ai/how-it-works-together/ - Module catalog: https://orkie.ai/modules/ - Pixel Analytics: https://orkie.ai/modules/pixel/ — Know who your visitors are and which ads really sell - CRM: https://orkie.ai/modules/crm/ — Spot your best prospects and follow up with them at the right time - Communications Center: https://orkie.ai/modules/comm-center/ — Every customer conversation in one inbox, with AI that drafts for you - Creative Studios: https://orkie.ai/modules/creative-studios/ — Turn your videos and products into content, ready to approve - Data Pipeline: https://orkie.ai/modules/data/ — Move, clean, and organize your data so every module can use it - Google Ads: https://orkie.ai/modules/google-ads/ — Feed Google real sales and fix tracking so your ads learn faster - Google Search Console: https://orkie.ai/modules/google-search-console/ — See what you rank for and what to fix next - Gmail: https://orkie.ai/modules/gmail/ — Your Gmail inside the shared inbox, with you in control - Projects: https://orkie.ai/modules/projects/ — Tasks, chat, and AI teammates in one place - YouTube: https://orkie.ai/modules/youtube/ — Put the right videos on your product pages and know which ones sell - Facebook & Instagram: https://orkie.ai/modules/facebook-instagram/ — Real sales back to Meta and every comment answered - TikTok: https://orkie.ai/modules/tiktok/ — Send TikTok real sales and keep spend honest - LinkedIn: https://orkie.ai/modules/linkedin/ — Count LinkedIn in your return on ad spend - Microsoft Ads: https://orkie.ai/modules/microsoft-ads/ — Real sales back to Microsoft and tracking fixed automatically - Google Merchant Center: https://orkie.ai/modules/merchant-center/ — Know the moment a product is disapproved - ChatGPT Ads: https://orkie.ai/modules/chatgpt-ads/ — Real sales back to ChatGPT Ads, with spending limits - Shopify: https://orkie.ai/modules/shopify/ — Your store, live in Orkie, with pop-ups and offers that protect margin - BigCommerce: https://orkie.ai/modules/bigcommerce/ — Your BigCommerce store live in Orkie, with attribution built in - Slack: https://orkie.ai/modules/slack/ — Get told in Slack when something happens - Gorgias: https://orkie.ai/modules/gorgias/ — AI-suggested replies inside Gorgias, with a full history in Orkie - Zendesk: https://orkie.ai/modules/zendesk/ — AI-drafted replies for your Zendesk tickets - IMAP/SMTP Email: https://orkie.ai/modules/imap-smtp/ — Any mailbox in the shared inbox, sent through your own server - Microsoft Mail: https://orkie.ai/modules/microsoft-mail/ — Microsoft 365 and Outlook mail in your shared inbox - AI Assistant: https://orkie.ai/modules/ai/ — An assistant that answers from your business and asks before it acts - AI Store Shopper: https://orkie.ai/modules/ai-store-shopper/ — Find out why a product is not selling, then check if the fix worked - Acumatica ERP: https://orkie.ai/modules/acumatica/ — Your ERP stock and orders, visible to the assistant and your store - Workspace MCP: https://orkie.ai/modules/workspace-mcp/ — Tell Claude or ChatGPT what you want and it does it in your workspace - QuickBooks: https://orkie.ai/modules/quickbooks/ — Count phone and in-person sales in your marketing results - SMS: https://orkie.ai/modules/sms/ — Text customers from the same place you email them - Newbook: https://orkie.ai/modules/newbook/ — Bring bookings and guests into your marketing picture - The Pixel: https://orkie.ai/pixel/ - Who it's for: https://orkie.ai/for/ecommerce/, https://orkie.ai/for/shopify/, https://orkie.ai/for/bigcommerce/, https://orkie.ai/for/retail/, https://orkie.ai/for/hospitality/, https://orkie.ai/for/b2b/, https://orkie.ai/for/services/, https://orkie.ai/for/agencies/ - How it works together (the flywheel): https://orkie.ai/how-it-works-together/ - Videos: https://orkie.ai/videos/ - How to start: https://orkie.ai/pricing/ - Customers: https://orkie.ai/customers/ - About: https://orkie.ai/about/ - What we believe (mission): https://orkie.ai/what-we-believe/ - Contact: https://orkie.ai/contact/ ## How the pieces work together (the flywheel) 1. Track every visitor and sale: Every visit, product view and verified order, counted on your own site by the Orkie pixel. Result: You know what really sells. 2. Your products, services and data, everywhere: What you sell and the data behind it, cleaned up by AI and sent to Google, Microsoft, Meta, TikTok and ChatGPT. What sells gets pushed; what only draws clicks gets pulled. Result: Ad budget follows real orders. 3. Smarter service and product suggestions: "Goes with" and "you may also like" follow your rules, for products and services, and you can see what they sell. Result: Bigger orders you can measure. 4. Ads to the right people: Your real buyer lists become ad audiences on Google, Meta and TikTok, consent checked. Result: Stop paying to reach people who already bought. 5. Emails that bring customers back: One personal email about what each customer looked at, left behind or is ready to buy again. Result: Customers come back. 6. Work that gets done: Every task, approval and project on one board, shared by your team and your AI agents. Result: Nothing slips, and your team gets time back. 7. A company brain that remembers: It keeps what worked, what didn’t and why, and feeds it into the next campaign, the next email and the next task. Result: Every turn starts smarter. The company brain feeds what it learns back to the pixel, the feeds and the next email, so each turn starts smarter. Details: https://orkie.ai/how-it-works-together/ ## What customers say - Lorin, Great Furniture Deal (Ecommerce): "Rich and our Orkie workspace are always watching which products are selling, and the campaigns move with them. When a brand starts picking up, it's getting pushed within hours, not weeks. And when a number doesn't look right, Rich tells me what's really going on." - Sabina, Hott Exhaust (Ecommerce): "Our catalog is a headache, with fitment and California rules on top of it. Ed and Rich work with me directly. Our workspace keeps the supplier data flowing into the store, Orkie built us a custom add-on that puts the right oversize handling fee in the cart based on each part's size, and now they're building a check so parts we can't ship to California can't be ordered. It feels like having our own team." - Larry, House of Holiday (Ecommerce): "Christmas is our whole year. The Orkie team runs our ads all season and builds our holiday landing pages, and our workspace tracks every order the ads bring in, so the weekly report tells me exactly where we stand and what's actually selling." - Gary, North Fork Resort (Hospitality): "We're a resort, and they built our workspace around how we actually work: guest check-in, our owner portal, our bookings, and the sales desk they're building for our team, all in one place. Gregg and Bryan listen first, then build it. It's our system, not something we had to bend to fit." - Jonathan, WNW (B2B services): "Gregg's team handles our marketing and our website, and they're bringing AI into how our whole company works. They're people first. They learn how we do things, then let AI take over the parts that slow us down." - Jesse, Torque King (Ecommerce): "We switched from Klaviyo to Orkie for email and haven't looked back. Our workspace sees what each customer looked at, so every email is about their parts, and Gregg and Bryan built it with us, not just for us. It costs us less and our email revenue is up. In the first ten days, abandoned-cart emails alone brought in seven orders." - Marc, Out East Marketing (Agency): "As a content agency, we juggle a lot of clients and a lot of moving parts. We're moving our work into our own Orkie workspace, with every project and task in one place and AI helping us keep it all moving. And Gregg's team treats us like part of their team." - Teddy, PremiereRad Solutions (B2B services): "I'm a rad tech who started a staffing company, not a web person. Orkie and the team are building our new site with me, and the AI company brain learns how our business works, so the blog posts from their creative and design studio sound like us and answer what facilities and techs actually ask. They connected Google Search Console too, so now we can see how people are finding us." - Nick, Master Spa Parts Online (Ecommerce): "Filters and parts are our business, and the numbers have to be right. Rich runs our Google and Microsoft campaigns, Ed keeps our product feeds clean, and our Orkie workspace tracks every order, so we know what's really selling. Every week I ask Claude for our numbers straight from the workspace, and when something doesn't add up, the team digs in and tells me what's really going on. We just started on the Outbox too, so our emails will be about the exact filter or part each customer needs, right when they need it." - Robbie, RY Enterprise (Agency): "I run the ads for my retail clients, and I need numbers I can stand behind. Each client gets its own Orkie workspace with the pixel, the product feed and a projects board, so I see which campaigns really bring in orders instead of what the ad platforms claim, and now we're bringing in the phone orders too. Ed works with me whenever a client needs help in the workspace, so I can stay on the ads." All quotes: https://orkie.ai/customers/ ## Knowledge base - What is an Orkie workspace?: https://orkie.ai/kb/what-is-a-workspace/ — Your private home for tracking, customer data, campaigns, and an AI assistant. Here is what lives inside and who can see what. - How modules work: https://orkie.ai/kb/how-modules-work/ — Modules are the building blocks of your workspace. Install what you need, connect an account, and they start sharing data with each other. - Talking to your workspace with Claude or ChatGPT: https://orkie.ai/kb/talking-to-your-workspace-with-claude-or-chatgpt/ — Connect Claude or ChatGPT once and ask your workspace anything. Reports, campaigns, and approved actions, with guardrails built in. - How the pixel works: https://orkie.ai/kb/how-the-pixel-works/ — First-party tracking for your store or website. What the pixel records, how it respects consent, and why owning the data matters. - Attribution explained: https://orkie.ai/kb/attribution-explained/ — The attribution models Orkie offers, how lookback windows work, why each sale is counted once, and how to reconcile with platform reports. - The shared inbox and AI drafts: https://orkie.ai/kb/the-shared-inbox-and-ai-drafts/ — One inbox for every channel, AI drafts grounded in real order data, and approval settings you control inbox by inbox. - CRM, audiences, and consent: https://orkie.ai/kb/crm-audiences-and-consent/ — Contacts, companies, journeys, deals, and audiences in one customer index. Consent is checked at send time and activations need approval. - Orkie for agencies: https://orkie.ai/kb/for-agencies/ — One login, a workspace per client, shared playbooks, honest reporting, white-label options, and operators who extend your team. - Custom modules and integrations: https://orkie.ai/kb/custom-modules-and-integrations/ — Anything you can describe can become a module. Connectors for ERPs, helpdesks, QuickBooks, Slack, and API keys for your own tools. - Security, privacy, and data ownership: https://orkie.ai/kb/security-privacy-and-data-ownership/ — Your data stays in your workspace and belongs to you. How access, consent, approvals, audit trails, and deletion work at Orkie. - Getting started with Orkie: https://orkie.ai/kb/getting-started/ — How getting started works: first call, workspace created, pixel installed, accounts connected, first report, first campaign, and operator check-ins. - Frequently asked questions: https://orkie.ai/kb/faq/ — Fifteen short answers about who Orkie is for, what it supports, how operators work, and how to get started. ## Blog - Related products that actually fit: https://orkie.ai/blog/related-products-that-actually-fit/ — Most "you may also like" widgets guess. Set related-product rules in plain words, like same brand or parts that fit, and measure what they really sell. - How to get your products into ChatGPT answers: https://orkie.ai/blog/how-to-get-your-products-into-chatgpt-answers/ — What AI assistants read, how to feed them one clean catalog, and how to see the sales ChatGPT, Gemini and Perplexity send you. - How Orkie's pieces work together: https://orkie.ai/blog/how-orkies-pieces-work-together/ — The pixel steers the feeds, measures related products and tells the Outbox what each shopper left behind. CRM lists become ad audiences. The company brain keeps learning. - How agencies run many stores from one place: https://orkie.ai/blog/how-agencies-run-many-stores-from-one-place/ — A private workspace per client, playbooks that carry across accounts, and reporting that reconciles to each store's real orders, not platform claims. - A CRM built from your pixel and your inbox: https://orkie.ai/blog/crm-built-from-pixel-and-inbox/ — Audiences from behavior rather than uploads, journeys the inbox can see, and outreach where consent is checked at the moment of sending, every time. - YouTube, TikTok and Instagram for stores: which videos actually sell: https://orkie.ai/blog/youtube-tiktok-instagram-which-videos-sell/ — Map videos to products, put the right video on the product page, and read the sales association honestly with direct, assisted and unknown labels. - Sending verified orders back to Google and Microsoft: https://orkie.ai/blog/sending-verified-orders-back-to-google-and-microsoft/ — Why the platforms should bid on your real sales. How verified uploads, hashed identifiers, refunds and consent work between the pixel and your ad accounts. - Talking to your store from Claude or ChatGPT: https://orkie.ai/blog/talk-to-your-store-from-claude-or-chatgpt/ — The questions an owner can ask, the actions they can take, the approvals that gate them, and how custom work gets built from the same chat window. - Running your customer inbox with AI drafts and human approval: https://orkie.ai/blog/customer-inbox-ai-drafts-human-approval/ — A day in a shared inbox: email and social comments in one list, AI drafts written with the order in front of them, and a person who approves every send. - One catalog, every channel: how feed quality decides who sees your products: https://orkie.ai/blog/product-feed-quality-one-catalog-every-channel/ — The channel reads your feed, not your store. One prepared catalog, rules written once, outputs per channel, and labels built from what the pixel says sells. - How a store uses multi-touch attribution to move budget: https://orkie.ai/blog/multi-touch-attribution-moving-budget-between-channels/ — Read first click, last click and position-based side by side, then move money between Google, Microsoft, Meta and TikTok one bounded step at a time. - Installing a pixel on your own domain: what changes in week one: https://orkie.ai/blog/installing-a-first-party-pixel-what-changes-in-week-one/ — Sessions, sources, orders matched and the ad-blocker gap. A day-by-day walk through the first week after a first-party pixel goes live on a store. - Why every ad platform claims the same sale: https://orkie.ai/blog/why-every-ad-platform-claims-the-same-sale/ — Google, Meta and TikTok each count the sale they touched. Why the numbers overlap, what the tags miss, and how a pixel on your own domain gives you one count. ## Facts - Founded 2012 as Sales & Orders; Orkie launched 2026. - Google Premier Partner awards (2017 to 2019), Microsoft Advertising Partner awards (2019 to 2021), BigCommerce Technology Partner award (2020). - Contact: hello@orkie.ai, 1-877-ORKIE-15 (+1-877-675-4315) # What is an Orkie workspace? The short version An Orkie workspace is a private space that belongs to one business. Everything Orkie does for you happens inside it. Your website tracking, your ad accounts, your customer list, your shared inbox, your projects, and your AI assistant all live there. Think of it as a building with your name on the door. Orkie provides the building. You decide what goes in each room and who gets a key. What lives inside a workspace A new workspace starts nearly empty. You add capability by installing modules. Each module does one job well and shares what it learns with the others. Common modules include: Pixel. Records visits, clicks, forms, carts, and orders on your site.Ads connectors. Link Google, Meta, and other ad accounts so spend and results sit next to your sales.Feeds. Prepare product feeds for shopping channels.CRM. Your contacts, companies, deals, and audiences.Communications Center. A shared inbox for email, chat, and marketplace messages, with AI drafts.Creative Studios. Where ad and content assets are planned and produced.Projects. Tasks and boards for you, your team, and your AI teammate.Commerce and finance. Shopify, BigCommerce, and QuickBooks connectors.Social and video. YouTube and other channel connectors.Slack. Alerts and summaries where your team already talks. You do not need all of these. Many businesses start with the pixel, one commerce connector, and one ad connector. One workspace, one business Each workspace holds one business's data and nothing else. A workspace never sees another workspace. If you run several brands, each gets its own workspace. Agencies get a workspace per client and switch between them from one login. This matters for trust. When your AI assistant or a team member asks a question, the answer can only come from your workspace. Who can see what Access is set by role. There are three kinds of people, plus your AI assistant, that can look inside. Admins. Usually the owner and one or two senior people. Admins install modules, connect accounts, invite people, set permissions, and approve high-impact actions.Team members. Everyone else you invite. Each person sees only the modules and data their role allows. A support agent can work the inbox without seeing ad spend. A media buyer can see attribution without reading customer emails.Orkie operators. The Orkie people who do the work for you. They see what they need to run your account and nothing more. More on this in the security article.Your AI assistant. When you connect Claude or ChatGPT through Workspace MCP, the assistant acts with your permissions, not more. It can read what you can read. It can only change things you are allowed to change. Deleting or merging customer records also needs a second admin. Permissions in plain terms Two settings cover most cases: Read business data. The person or assistant can ask questions and see reports.Execute approved actions. The person or assistant can also make changes, such as sending a reply or activating an audience, within the approval rules. Most team members only need the first. Grant the second when someone actually needs to act, and remove it when they no longer do. Access can be revoked at any time and takes effect on the next request. How the pieces connect Modules talk to each other so you do not have to copy data around. A sale recorded by the pixel appears on the customer's CRM timeline. A customer email in the inbox shows their recent orders beside the draft reply. A task raised from an inbox conversation lands in Projects with a link back to the original message. You get one picture of each customer and each campaign instead of eight tabs that disagree. What a workspace is not A workspace is not a dashboard you have to learn on your own. Orkie's operators set it up, keep it healthy, and run campaigns inside it. It is also not a data broker. Nothing in your workspace is sold, pooled, or used to train models for anyone else. Next steps If you want to see a workspace with your own data in it, talk to us. If you have questions first, contact us. --- # How modules work Modules are the building blocks of your workspace A workspace on its own is an empty room. Modules are what you put in it. Each module adds a set of pages, a set of abilities, and its own data. The pixel module records site activity. The CRM module keeps contacts. The ads connectors bring in spend and performance. You pick from the module catalog, with two twists. Every module is built or reviewed by Orkie, and most businesses never install anything themselves. Your operator does it during setup and adds more as your needs grow. Installing a module Installing takes minutes, not weeks. An admin or your operator picks the module from the catalog.The module is added to your workspace with its own pages and settings.If the module needs an outside account, you connect it (see below).The module starts collecting or syncing. Most show useful data the same day. Nothing about installing one module affects another. You can add the shared inbox this month and Creative Studios next quarter. What "connected" means Many modules link to a service you already use: Shopify, Google Ads, Meta, QuickBooks, Slack, YouTube. Connecting means you sign in to that service and grant Orkie permission to read, and sometimes write, on your behalf. A few things to know: You stay in control. The connection uses the service's own approval screen. Orkie never asks for your password.Permission is specific. A connector asks only for what its module needs. The ads connector cannot touch your store. The store connector cannot touch your ads.You can disconnect at any time. Revoking access stops the sync. It does not delete the data already in your workspace unless you ask for that too."Connected" is visible. Every connector shows whether it is healthy, when it last synced, and whether anything needs attention. How modules share data This is where Orkie is different from a pile of separate tools. Modules pass information to each other inside your workspace so each one gets smarter. Some examples you will see in practice: Pixel feeds CRM. When the pixel identifies a visitor through a form, a login, or a purchase, that activity appears on the person's CRM timeline. You see the ad they clicked, the pages they viewed, and what they bought, in one place.CRM feeds ad audiences. Build an audience in CRM, such as "bought twice, not in the last 90 days." With approval, that audience can be sent to your ad platforms for retargeting or exclusion.Commerce feeds the pixel. Orders from Shopify or BigCommerce confirm what the pixel saw in the browser. Refunds flow back so revenue numbers stay honest.Inbox feeds Projects. A customer email that needs follow-up becomes a task in Projects with a link back to the conversation. No copying and pasting.Inbox reads commerce. When a customer asks where their order is, the draft reply already knows the order status.Everything feeds your AI assistant. Ask a question in Claude or ChatGPT and the answer can draw on any installed module you have permission to see. Sharing is deliberate and bounded. A module can only see what another module chooses to share. Your data stays separate from every other business. It only goes out to the services you connect, through actions you approve. Turning things off You can switch a module off without uninstalling it. Its pages disappear from the menu, its syncs pause, and other modules stop receiving its updates. Turn it back on and it picks up where it left off. Uninstalling goes further. The module is removed and its data can be wiped on request. Your operator will confirm what is affected before doing it, because other modules may rely on that data. Two more switches worth knowing: Per-user access. An admin can hide a module from specific roles without turning it off for everyone.Kill switches. Some abilities, such as AI drafting in the inbox, have a workspace-wide switch that overrides every individual setting. Useful when you want to pause something fast. Custom modules If the catalog does not cover a need, Orkie can build a module for you. You describe the job in plain language. Orkie builds it, reviews it, and installs it in your workspace like any other module. See the article on custom modules and integrations for details. Getting started Your operator will suggest a starting set of modules on the first call based on how you sell and where you advertise. Talk to us or contact us to talk it through. --- # Talking to your workspace with Claude or ChatGPT What Workspace MCP is Workspace MCP is a secure door between an AI assistant you already use and your Orkie workspace. Connect Claude, ChatGPT, or both. Then talk to your business the way you would talk to a sharp analyst who has read everything. You do not learn a new chat tool. You use the one you already have. Connecting once An admin turns on Workspace MCP and copies a connector address. Each approved person adds that address to their Claude or ChatGPT settings and signs in with their normal workspace login. That is it. A few things this design gets right: The address is not a secret. Every person authenticates as themselves.The assistant gets only that person's current permissions. Change the person's role and the assistant changes with it.Each connection can be removed on its own. Revoke a laptop without revoking the person. What you can ask Anything your installed modules know. Some real examples: "How many sales did we get today, and which sources drove them?""Which YouTube visitors bought something this month?""Compare Shopify sales with Google Ads spend by week.""Show me products missing required feed fields.""Which customers have opened three support conversations in 30 days?""What tasks are assigned to me? Overdue first.""What would our AI reply to this email, and what sources would it use?" Every answer comes from your workspace data. If the data is not there yet, the assistant can ask a connected module to fetch it, but it cannot invent access or quietly connect to something new. The assistant can also tell you whether an answer came from saved data or a live request, and how fresh it is. What it can do Beyond questions, the assistant can prepare and carry out work: Draft a customer reply grounded in their order history.Prepare a new product feed with the fields you specify.Build a CRM audience from rules you describe, with a preview first.Create tasks in Projects and load the full context of a task assigned to you.Compare an attached product image with your catalog.Outline a campaign and set up the pieces across modules.Start a sync or refresh when a module offers one. How approvals work Reading is instant. Changing something is treated with care. The rule is simple: the assistant shows you the exact effect and the business reason before anything happens. Low-risk changes like adding an internal note. A clear request in the conversation is enough.Medium-risk changes like refreshing a report or moving a recommendation forward. The assistant states what will happen and asks once. "Yes" or "send it" is the final answer. It will not ask twice.Permanent changes to customer records, like deleting or merging them. These stay pending until a different workspace admin approves the exact action in workspace settings. The assistant cannot approve its own work. Every action is frozen to one module, one set of details, and one request. It can run once. If anything changes, the assistant has to show you the new effect and ask again. Vague instructions like "spend whatever you think is right" are blocked, not interpreted. What it never does Workspace MCP is designed around limits. Your assistant: Never touches a raw database. It works through bounded, structured reads.Never sees passwords, ad account credentials, or connector secrets.Never reaches another workspace.Never gets access to code, servers, files, or deployment tools.Never acts on standing permission. Each action needs its own clear authorization. If a module is missing or turned off, the related abilities simply disappear rather than falling back to something broader. Example prompts to try Once connected, paste one of these into a new chat: "Use the Workspace connector. First check what it can reach and whether any data is stale.""Give me a Monday morning report: revenue, ad spend, ROAS, and the three biggest changes since last week.""Which customers are in our 'lapsed VIP' audience and what did they last buy?""Draft a reply to this email using our support tone. Show me before sending.""Prepare a Google Shopping feed with title, price, availability, and GTIN. Do not publish it yet.""What is assigned to Claude for me? Load the first task." Getting set up Workspace MCP is included when Orkie sets up your workspace. Your operator will walk you through connecting your assistant on the first call. Talk to us to see it live, or contact us. --- # How the pixel works What the pixel is The Orkie pixel is a small piece of code that runs on your website or store. It notices what visitors do, sends that activity to your workspace, and turns it into sessions, journeys, and sales you can actually use. It is first-party. The pixel belongs to you and reports to your workspace, not to an ad network. That distinction shapes everything else in this article. Installing it Installation depends on where you sell. Shopify. Orkie provides a custom pixel that installs through Shopify's own pixel settings. No theme editing. It also listens for orders and refunds directly from Shopify so revenue is confirmed, not guessed.BigCommerce. A script is added once in your store settings. Orders are confirmed through the store connection.Any other website. A single tag goes in the site header. Works with WordPress, Webflow, Squarespace, custom builds, and landing pages. Your operator handles this during setup. Most sites are live within the hour, and a heartbeat indicator shows you the pixel is reporting. What it records The pixel captures the events that explain how people find you and what they do next: Page views and the source of the visit, including ad click identifiers and referral codes.Product views, add to cart, checkout steps, and purchases.Site search queries and whether they led to a sale.Form starts, submissions, and abandonments.Video and content engagement where applicable.Cart, checkout, and payment abandonment. From those events the workspace builds visitors, sessions, and attribution history. Returning visitors are linked across visits. Where a customer logs in or buys, the pixel can link web activity to the same person in your point of sale or phone orders, so you see one customer, not three strangers. Forms and leads on non-store sites Not every business sells in a cart. Service businesses, B2B companies, and lead-generation sites get the same treatment. The pixel tracks the form lifecycle, detects when a submission contains an email or phone, and records it as a lead. That lead appears in the CRM with the pages and source that produced it. Attribution works for leads exactly as it does for orders. Consent and privacy posture The pixel is built to respect the visitor's choice. Consent gates. Where a consent banner is in use, the pixel honors it. Declined visitors are not tracked for marketing purposes.Jurisdiction awareness. Consent policies can differ by region, and the workspace reports acceptance rates by jurisdiction so you know where you stand.Hashed identifiers. When conversions are sent to an ad platform for measurement, identifiers are hashed and consent is checked first.Visible health. A Consent and Health page shows your posture at a glance, and a data quality grade tells you if coverage drops. You keep control of what is sent where. Nothing is shared with a platform unless you have connected it and chosen to send. Why first-party matters Browsers and operating systems have spent years cutting off third-party tracking. Cookies expire faster, click identifiers get stripped, and platform pixels see less every quarter. The result is familiar: your ad platform says it drove 300 sales and your store says you had 180. First-party tracking sidesteps most of this. The data flows from your domain to your workspace. It lasts longer, it is more complete, and it is yours. You can: Measure every channel with the same yardstick instead of trusting each platform's own report card.Send clean, consented conversion data back to platforms to improve their bidding.Keep your history if you switch agencies, ad platforms, or store providers. What happens with the data Pixel data stays in your workspace, apart from the verified conversions you choose to send to your connected ad platforms. It powers the attribution reports, feeds customer timelines in the CRM, confirms revenue against store orders, tracks returns and their reasons, and gives your AI assistant something real to answer from. It is never pooled with other businesses. Common questions Does it slow my site down? No. The tag is small and loads after your content. Do I still need GA4? You can keep it. Many clients run both. The pixel is the one that ties spend to confirmed revenue and customers. What about my existing platform pixels? Keep them for platform-side optimization. The Orkie pixel gives you the independent view. Ready to see your own traffic through it? Talk to us or contact us. --- # Attribution explained The question attribution answers A customer sees a YouTube ad on Monday, clicks a Google search ad on Thursday, opens your email on Saturday, and buys on Sunday. Which channel gets the credit? Attribution is the set of rules you use to answer that. There is no single right answer, which is why Orkie gives you several models side by side rather than one number to argue about. The models Each model divides credit for a sale across the touches that came before it. First touch. All credit to the first visit. Best for understanding what introduces new people to your brand.Last touch. All credit to the final visit before purchase. Best for understanding what closes.Linear. Equal credit to every touch. A fair default when you want to see every channel that participated.Time-decay. More credit to touches closer to the sale, less to older ones. Useful for longer consideration cycles where recent nudges matter most.Position-based. Heavier credit to the first and last touch, with the remainder shared among the middle. Rewards both discovery and closing. Orkie also shows an "influenced" view. It answers a simpler question: did this channel appear anywhere in the journey? That is useful for channels like video and social that rarely close but often start the story. Lookback windows A lookback window is how far back Orkie looks for touches before a sale. A seven-day window ignores a visit from three weeks ago. A ninety-day window includes it. Choosing a window is a business decision: Short windows (7 to 14 days) fit impulse purchases and low prices.Medium windows (30 days) fit most stores.Long windows (60 to 90 days) fit considered purchases, B2B, and high prices. You can change the window and see how credit shifts. Big swings usually tell you something about how long your customers take to decide. Each sale is counted once This is the part most tools get wrong, and it is why platform reports never add up. Orkie holds a single record of each order. That record is confirmed against your store, so a test order, a duplicate event, or a browser refresh does not become a second sale. Refunds are applied back to the original order. Every attribution model then divides that one confirmed order across its touches. Orkie calls this a canonical order. Whatever model you look at, the total revenue is the same. Only the split changes. If you sum every channel under any single model, you get your real revenue, not 180 percent of it. Why platforms report more than you sold Each ad platform counts conversions its own way, and each one only sees its own touches. Some common reasons the numbers disagree: Overlap. Google and Meta both claim the same customer because both were in the journey.View-through credit. A platform counts a sale because someone saw an ad, even without clicking.Different windows. One platform uses 7 days, another uses 28.Modeled conversions. Platforms estimate sales they could not observe directly.Refunds. Platforms rarely subtract them. None of this makes platform reports useless. They are good at optimizing within their own walls. They are not good at telling you the whole story. Reconciling with what platforms report Orkie keeps the platform's numbers next to its own so you can see the gap and understand it. A practical way to read the comparison: Start from confirmed revenue in your workspace. That is the anchor.Look at each platform's claimed conversions beside its attributed share under your chosen model.Expect platforms to claim more. The size of the gap, and whether it is growing, is the signal.Use the "influenced" view to give credit to channels that start journeys but rarely finish them.Feed consented conversion data back to platforms so their optimization is based on real sales. Your operator reviews this with you and will recommend a primary model for decision making, usually position-based or time-decay for stores and first touch for lead generation. Where attribution shows up Attribution powers more than one report. Product pages show which sources sell which items. Customer records show the journey that produced each order. Audiences can be built from acquisition source. And your AI assistant can answer "which channel drove our best customers last quarter" without you exporting anything. Sales that arrive with no signal Sometimes an order has no traceable touch: a phone order, a walk-in, a marketplace sale. Orkie does not force these into a channel. They are reported honestly as unknown, with an explanation of why, and a mapping tool lets you classify recurring patterns so they land in the right place going forward. Want to see your own channels under all five models? Talk to us or contact us. --- # The shared inbox and AI drafts One inbox for every channel Customer conversations arrive from everywhere: email, marketplace messages, store chat, social comments, YouTube. Communications Center pulls them into one shared inbox so your team works from a single queue instead of six logins. Each conversation shows who the customer is, what they have bought, what they have asked before, and which team member is handling it. Assign, tag, add internal notes, and reply, all in one place. Channels and inboxes A channel is a source of messages, such as a support email address, a helpdesk like Gorgias or Zendesk, or a Shopify contact form. A channel appears when its connector module is installed. An inbox is a group you organize conversations into. You might have Sales, Support, Wholesale, and Returns. Each inbox has its own: Source channels that feed it.Default tags.Send-as address, so replies come from the right name.AI behavior setting (explained below). Routing rules decide which inbox a new conversation lands in. Exact rules based on sender, domain, subject, or source always win. When no rule matches, AI categorization can sort by intent. AI drafts When AI drafting is on, the assistant reads the conversation and proposes a reply. The draft appears beside the message. A team member can send it, edit it, or discard it. Drafts are written in your voice using skills you configure. Common ones include order status, returns and exchanges, product questions, and complaint handling. Each skill sets the tone, the rules, and the information the AI may use. How order data grounds replies The difference between a helpful draft and a generic one is context. Before drafting, the AI looks at what the workspace already knows: The customer's recent orders, shipping status, and refunds from your connected store.Their CRM record, including past conversations and notes.Your product catalog and policies.Any rules the inbox or skill defines. So when someone asks "where is my order," the draft names the order, the carrier, and the expected date. It does not guess. If the information is missing, the draft says so and the AI flags it rather than filling the gap. Every draft keeps a source trace. You can see which records and rules it used. Your AI assistant in Claude or ChatGPT can also preview what the workspace AI would say to an email you paste, along with its sources. Approval gates and auto-send You decide how much the AI is allowed to do, one inbox at a time. Off. No drafts. Use this for legal, executive, or sensitive inboxes where every reply is hand-written.Draft only. The AI proposes, a person sends. This is the default and the right choice for most inboxes.Auto-send. The AI writes and sends without review. Use this sparingly and only for narrow, predictable categories like order-status lookups where the grounding data is strong and a person is watching for outliers. A workspace-wide master switch sits above all of this. Turn it off and AI drafting stops everywhere, regardless of inbox settings. It is your kill switch. Some marketplace channels add their own layer. A reply may be held as pending until the marketplace's rules, quota, or approval requirements are satisfied. The inbox shows you when that happens and why. Escalation Not everything should be answered by a draft. The complaint-handling skill recognizes frustrated customers, adjusts its language, and can route the conversation to a person. Team members can escalate by assigning to a colleague, changing the inbox, or raising a task in Projects that links back to the conversation. Alerts can also go to Slack so the right person sees a hot conversation without living in the inbox. Automated follow-ups Communications Center is also the sending arm for storefront follow-ups such as back-in-stock alerts, welcome emails, and cart-rescue offers. These messages only go out when the CRM confirms the person's consent at send time and the offer is still valid. An unsubscribe after signup blocks the later message. Working with your operator Orkie operators can staff your inbox, tune skills, and review draft quality over time. Many clients start with drafts only, measure how often drafts are sent unchanged, then move a category or two to auto-send once they trust it. See it with your own messages: talk to us or contact us. --- # CRM, audiences, and consent The CRM is your customer index Every other module knows something about your customers. The pixel knows what they browsed. The store knows what they bought. The inbox knows what they asked. The CRM is where those threads come together into one person. It does not replace those modules. It links to them. Open a contact and you see a single timeline built from every source, without anyone copying data by hand. What lives in the CRM Contacts. People, with identity links to their store account, email, phone, and web visitor record. Duplicate submissions do not create duplicate people.Companies. For wholesale, B2B, and agencies. Contacts belong to companies, and company records roll up activity.Journeys. The timeline of every touch: ad click, page view, form, order, conversation, note.Deals. A pipeline for sales that take more than a cart. Stages, values, owners, and expected close dates.Activities and tasks. Calls, meetings, and follow-ups. Follow-up tasks are real Projects tasks, so they show up in the same place as the rest of your team's work.Custom fields. Add whatever your business needs to track.Relationship ratings and roles. Star ratings and roles you set by hand stay as you set them. Automation never overwrites a human decision. Contacts can be created automatically when a module sees a real person, such as a form submission with an email or a first order. Audiences An audience is a saved set of contacts defined by rules. Examples: Bought two or more times, no purchase in 90 days.Signed up for a back-in-stock alert on a product that just arrived.Came from YouTube and spent over a threshold.Opened a support conversation in the last week. Rules can use purchase history, web behavior, storefront intent signals, conversation history, custom fields, and consent status. Audiences update as people qualify or fall out. Every audience is previewed before it is saved so you know exactly who is in it. Consent is checked at send time This is the most important rule in the CRM. Being in an audience is not the same as being allowed to receive a message. Consent is recorded only when the person actually opted in. A back-in-stock request or a help form does not create marketing permission. A separately checked marketing box does, with its evidence.Your workspace chooses whether marketing email requires confirmed double opt-in or allows single opt-in.Immediately before any automated message sends, the CRM checks consent and suppression again. If the person unsubscribed after joining the audience, the message does not go.Discount codes for offers are kept protected and released to the sending module only when the offer is still valid. The result is that you can build audiences freely, knowing the send step enforces the rules. Activating audiences to ad platforms Audiences are useful beyond email. You can send one to Google, Meta, or another connected ad platform for retargeting, lookalike seeding, or exclusion. Activation is treated as a high-impact action because it moves customer data outside the workspace. You or your AI assistant define the audience and preview it.The activation request states exactly which audience goes to which platform and why.You approve the exact request.The workspace checks everything again and sends identifiers to the platform in hashed form, respecting consent. If CRM access is turned off for a user or a connection, the action is simply unavailable. There is no fallback path around the approval. Asking your assistant With Workspace MCP connected, the CRM answers questions in plain English: "Who are our top 50 customers by lifetime value and when did they last buy?""Build an audience of people who bought the blue model but never the accessory kit. Preview it.""Add a note to this contact that they asked for a manager callback." Reads happen instantly. Edits to contacts and audiences follow the same approval rules as everything else. Goals and insights Set goals for revenue, new contacts, or deals won, and watch progress on the Insights page. Because the CRM sees every module, the numbers reflect confirmed orders and real conversations, not estimates. Working with your operator Orkie operators set up your identity rules, consent settings, and first audiences during onboarding, then maintain them. If your list has history in another tool, they will plan the import with you. Talk to us to see a customer timeline built from your data, or contact us. --- # Orkie for agencies Built for people who run many accounts Agencies live in a dozen tools per client, multiplied by every client. Orkie gives you one login and one way of working across all of them, while keeping each client's data fully separate. One login, a workspace per client Every client gets their own workspace. Their pixel, their ad connectors, their CRM, their inbox. You switch between workspaces from a single account. What this gives you: Clean separation. No risk of one client's audience touching another's ads. A workspace cannot see another workspace.Clear ownership. The client's data belongs to the client. If the relationship ends, the workspace goes with them, along with its history.Role control. Give your media buyer access to attribution across ten clients and your support lead access to inboxes across three, without either seeing the rest. Your Claude or ChatGPT connection works the same way. Each workspace connects on its own, and the assistant only reaches the one you are talking to. Shared playbooks Setup should not start from zero for each client. Agencies keep playbooks in Orkie: the module set for a store client, the audience rules for a lapsed-customer campaign, the inbox skills for a support tone, the reporting layout your account managers use. Apply a playbook to a new workspace and adjust from there. Custom modules built for one client can, with that client's agreement, become part of your playbook for others. Reporting your clients will trust The recurring agency problem is that every platform reports its own wins and the client's accountant sees a different number. Orkie reports from confirmed revenue in the client's store, attributed under a model you choose, with the platform's own claims shown beside it. Reports can be pulled on a schedule, sent to Slack, or asked for in plain English through your assistant: "Give me the weekly summary for this client with spend, confirmed revenue, ROAS, and what changed." The same question works in every workspace. White-label options Orkie can sit behind your brand. Client-facing reports, the workspace login, and notification emails can carry your name. Talk to us about what your clients should and should not see. How the operator team fits Orkie's operators do the work inside workspaces. For agencies this is flexible: You run everything. Orkie provides the workspace and support. Your team does the work.Operators handle the plumbing. Orkie installs pixels, connects accounts, maintains feeds, and keeps data healthy. Your team does strategy and creative.Operators extend your team. Orkie staffs inboxes, builds audiences, runs campaigns, and produces reports to your standard, under your account management. Many agencies start with the second option and add the third for clients that outgrow their capacity. Approvals that protect you Agency staff make changes in client accounts all day. Orkie's approval rules apply to everyone: any action that sends to customers, moves money, or pushes data to an ad platform waits for a person to approve the exact request. Make the client an admin and they can sign off themselves, instead of an email chain. Deleting or merging customer records needs a second admin. Every action is logged with who asked, who approved, and what happened. Bringing a client on A typical onboarding looks like this: Scope call. We map what the client sells, where they advertise, and what they need to see.Workspace created. Usually the same day, with your playbook applied.Pixel installed and accounts connected. Store, ad platforms, email, and any other channels. Operators handle the installs with the client's approval screens.Data check. Within a few days, confirm the pixel matches store orders and connectors are healthy.First report. A baseline the client can hold you to.Ongoing. Regular operator check-ins with your account manager. We move as fast as each client's setup allows. If you need something for a client, ask Orkie in the client's workspace, add a task on that workspace's Projects board and assign it to our support agent, or message us in Slack if we share a Slack channel with you. Who this is for Orkie fits performance agencies, ecommerce specialists, and marketing consultancies that manage several client accounts and want one operating system for all of them. It does not fit agencies looking for a media-buying tool alone. Talk to us with a client account in mind, or contact us to talk about partnership terms. --- # Custom modules and integrations Anything you can describe Every business has a process that no off-the-shelf tool handles. A wholesale reorder rule. A returns workflow tied to a specific carrier. A weekly report your board expects in a particular shape. In Orkie, those become modules. A custom module is a real module in your workspace, with its own pages, data, and abilities, that shares data with everything else exactly like the standard ones. How a custom module gets built There are two paths, and they can work together. Built by Orkie. You describe the job in plain language to your operator. Orkie scopes it, builds it, reviews it for security and quality, and installs it in your workspace. You test it. If something needs to change, you say so.Requested through your AI assistant. With Workspace MCP connected, you can describe what you need in Claude or ChatGPT. The request is captured as a build request in your workspace. Orkie's build process picks it up, and the result goes through the same review and install steps as anything else. In both cases, nothing goes live in your workspace without review. You do not need to hire a developer, write a specification, or manage a project. What people ask for Some examples of custom modules built for clients: A restock planner that watches sell-through and drafts purchase orders.A wholesale portal where trade customers see their pricing and reorder.A dealer locator that feeds leads to the right regional rep.A quality report that turns return reasons into supplier scorecards.A rules engine for shipping promotions across two stores. If you can explain it to a smart new hire, you can explain it to Orkie. Connectors to systems you already run Connectors are modules that link to an outside system. Orkie maintains a growing set and builds new ones when needed. Commerce. Shopify and BigCommerce are supported out of the box for orders, products, customers, refunds, and storefront forms. Accounting. QuickBooks brings offline and manual orders into your workspace so attribution and customer value include sales that never touched the website. It also keeps revenue reporting honest across channels. ERP. For businesses with an ERP such as Acumatica, a connector syncs inventory, orders, and customer records so your workspace reflects the system of record rather than a copy of it. Helpdesk. If your support team lives in Gorgias or Zendesk, a connector brings those conversations into the shared inbox and customer timeline, or sends Orkie's context to the helpdesk, depending on which you want to be the front door. Slack. Alerts, daily summaries, hot conversations, and approval requests go to the channel you choose. Your team stays where they already are. Ads, social, and video. Google, Meta, YouTube, and other platforms for spend, performance, audiences, and content. Each connector goes through the platform's own permission screen. You grant access, you can see the connection's health, and you can revoke it at any time. API keys for your own tools Some businesses have internal tools or a developer on staff who wants to pull data from the workspace or push events in. Orkie supports this with workspace API keys. At a high level: An admin creates a key with a name, a set of permissions, and an expiry date.The key can read what its permissions allow and nothing more. It cannot reach another workspace.Every request is logged and the key can be revoked in one click. Your operator will help scope what a key should be able to do. Most integrations only need read access. What custom work does not do Custom modules run inside the same guardrails as everything else. They cannot bypass approvals for sends and money-affecting actions. They cannot reach outside your workspace. They are reviewed before install and monitored after. A custom module is a first-class citizen, not a back door. Getting started Bring your list of "I wish it could just" items to the first call. Some of them are already modules. The rest are a conversation away. Talk to us or contact us. --- # Security, privacy, and data ownership The principle Your data belongs to you. It lives in your workspace, it is used to serve your business, and it goes nowhere else. Everything in this article follows from that. Your data stays in your workspace Each workspace is a private, separate space. No workspace can see another. No report, audience, or AI answer can draw on data from a different business. There is no shared pool, no benchmark built from client data, and no training of models on your records for anyone else's benefit. When you connect a service, data flows between that service and your workspace only. Orkie does not resell, license, or share it. First-party tracking The Orkie pixel reports from your domain to your workspace. It is not an ad network's tracker in disguise. That means: You decide which platforms, if any, receive conversion data.Anything sent to a platform for measurement is hashed and gated by consent.If you leave a platform, an agency, or Orkie, your history is still yours. Consent is enforced, not just recorded Recording consent is easy. Honoring it every time is the hard part. The pixel respects your consent banner. Declined visitors are not tracked for marketing.Marketing permission is recorded only when a person actually opts in through a separate, clearly labeled choice.Before any automated message sends, the CRM checks consent and suppression again. An unsubscribe after signup blocks the message.Your workspace chooses single or confirmed double opt-in.Consent posture and acceptance rates are visible by region so you can see your standing at any time. Who at Orkie can see what Orkie operators need access to do the work you have hired them to do. That access is deliberate and limited. Operators work inside your workspace under their own named accounts, not a shared login.Their access is scoped to the modules relevant to your engagement.Their actions appear in the same audit trail as your team's.They never see your passwords or connector credentials. Connections use each platform's own approval screen, and the resulting access is held by the workspace, not by a person.Engineering staff do not browse customer workspaces. Access for support or incident work is limited, logged, and time-bound. If you want a tighter arrangement, such as operator access to specific modules only, tell us and it will be set that way. Approvals and the audit trail Every action that changes something in your workspace is recorded: what was done, by whom, when, and on whose approval. Actions that carry real-world consequences (sending to customers, moving money, or pushing data to an ad platform) wait for a person to approve the exact request. An AI assistant cannot approve its own proposal. Permanent changes to customer records, like deleting or merging them, need a second admin: the person who asks cannot be the person who approves. An approved request is locked to its exact details and can run once. This applies to everyone equally: your team, your agency, Orkie operators, and any AI assistant connected to the workspace. What the AI assistant can and cannot reach When you connect Claude or ChatGPT, the assistant acts with your permissions and nothing more. It uses bounded, structured reads. It has no access to raw databases, credentials, code, servers, or other workspaces. Revoke a connection and it stops on the next request. No scraping Orkie gathers data through the pixel on your own site, through connections you approve, and through messages sent to you. It does not scrape competitor sites, harvest social profiles, or buy third-party lists. If a data source is in your workspace, it is there because you put it there. Deletion on request You can ask for any of the following at any time: Deletion of a specific person's data, to honor a privacy request.Removal of a module and its data.Export of your workspace data in a standard format.Deletion of the whole workspace. Your operator confirms the scope with you, because some data is shared between modules, and then carries it out. Exports are yours to keep. Security practices Data is encrypted in transit and at rest. Access requires authentication, and roles limit what each person can do. Sensitive values such as discount codes and connector tokens are stored protected and released only to the module that needs them at the moment it needs them. Errors and unusual activity are monitored so problems are caught early. Questions If your legal or IT team has a security questionnaire, we are happy to complete it. Contact us or raise it on your first call. --- # Getting started with Orkie How it starts There is no self-serve signup. Every Orkie client starts with a conversation, because the setup that works for a Shopify apparel brand is different from the one that works for a B2B manufacturer with an ERP. Here is the order things happen in. We move through it as fast as your setup allows, and if you need something along the way, ask Orkie in your workspace, add a task on your Projects board and assign it to our support agent, or message us in Slack if we share a Slack channel with you. Step 1: Get set up The first call. You talk to us. We look at how you sell, where you advertise, what tools you already run, and what you most want to know that you cannot see today. If Orkie is a fit, we agree on a starting set of modules and who your operator will be. Workspace created. Your workspace is set up with the agreed modules. You and any admins receive logins. Your operator introduces themselves and sets a check-in rhythm. Pixel installed. For Shopify, the custom pixel is added through your store settings. For BigCommerce or a regular website, a single tag goes in. Your operator confirms the pixel is reporting and that orders in the store match what the pixel sees. Accounts connected. You approve connections to your ad platforms, email, social and video channels, and accounting or helpdesk tools. Each one uses the platform's own approval screen. Your operator checks that each connection is healthy and syncing. From that point, your workspace is collecting real data. Step 2: Check the data Data quality check. Once some traffic has come in, it is enough to confirm that attribution, identity matching, and consent handling are working. Your operator reviews the data quality grade with you and fixes anything that is off, such as a form that is not being tracked or a channel showing as unknown. Connect your assistant. If you use Claude or ChatGPT, your operator walks you through connecting it. Your first question is usually "what can you see, and is anything stale?" Your second is usually about last week's sales. Inbox and CRM setup. If the shared inbox is part of your plan, channels are connected, inboxes are organized, and AI drafting is set to draft-only. Consent settings and the first audiences are configured in the CRM. Step 3: First report First report. This is your baseline. It shows confirmed revenue, spend by channel, attribution under the model you chose, and the gap between what platforms claim and what actually sold. Your operator walks you through it. Most clients learn something uncomfortable and useful on this call. Playbook decisions. Based on the baseline, you and your operator agree on the first things to act on. Common first moves: fix the biggest attribution gap, build a lapsed-customer audience, or move order-status emails to AI drafting. Step 4: First campaign First campaign. Something goes out the door. It might be a retargeting audience activated to an ad platform, a back-in-stock flow, a product feed to a new channel, or a creative set produced in Creative Studios. Your operator prepares it. You approve anything that sends or spends. Results show up in the same reports as everything else. Operator check-in. A review of the start: what was set up, what the data says, what is next. From here, check-ins settle into a regular cadence that fits your business. What you need to provide The list is short: Someone with admin access to your store or website to approve the pixel.Someone who can approve connections to your ad and channel accounts.Someone who approves changes, usually the owner or one senior person.Twenty to thirty minutes for each check-in. You do not need a developer, a data analyst, or a project manager. What you get from Orkie A named operator who knows your account.Setup, connections, and data health handled for you.Reports you can trust and a plain-English assistant that answers from them.Campaigns built and run inside your workspace, with approvals that keep you in control.The option to add modules, connectors, or custom builds as you go. Common questions at this stage Can I keep my agency? Yes. Many clients bring their agency into the workspace. See the agency article. What if I already have GA4 and platform pixels? Keep them. Orkie runs alongside and gives you the independent view. How long until I see reliable attribution? Numbers start the day the pixel goes live and get more reliable as orders come in. Longer purchase cycles take longer to fill in. If you need something sooner, ask Orkie in your workspace, add a task on your Projects board and assign it to our support agent, or message us in Slack if we share a Slack channel with you. Ready to start? Talk to us or contact us. --- # Frequently asked questions About Orkie 1. Who is Orkie for? Business owners, agency owners, and the marketing leads who work for them. If you sell online, in stores or by phone, or generate leads from a website, spend money on ads, and want one honest picture of what is working, Orkie is built for you. It fits businesses from a single store to an agency with dozens of clients. 2. What does "operators, not consultants" mean? A consultant tells you what to do and leaves. An Orkie operator does the work inside your workspace: installs the pixel, connects accounts, builds audiences, runs campaigns, staffs the inbox if you want, and produces reports. You get a named person who knows your account and shows up every week. Advice is included, but the point is execution. 3. Do you replace my agency? No, unless you want us to. Many clients bring their agency into the workspace. The agency gets clean attribution and reporting, and Orkie operators handle the plumbing so the agency can focus on strategy and creative. Some clients use Orkie instead of an agency. Both work. 4. Is there a free trial or self-serve signup? Not right now. Every client starts with a call so we can set up the right modules for how you sell. Talk to us to begin. Platforms and setup 5. Which platforms do you support? Shopify and BigCommerce for commerce. Google, Meta, YouTube, and other major ad and social platforms. QuickBooks for accounting. Slack for alerts. Helpdesks such as Gorgias and Zendesk. ERPs such as Acumatica. Any regular website for the pixel. If something you use is missing, ask. Connectors are added regularly and custom ones can be built. 6. Do I need developers? No. Orkie operators install the pixel and connect accounts. Custom modules are built by Orkie from a plain-English description. If you do have a developer who wants to pull data into your own tools, API keys are available. 7. Do I keep GA4? Yes, if you want it. Orkie runs alongside GA4 and platform pixels. The difference is that Orkie ties spend to confirmed store revenue and to real customers, and it keeps the data in your own workspace. 8. How long until I see data? The pixel reports within minutes of going live. Attribution gets more reliable as orders come in. Longer purchase cycles take longer to fill in. Connected accounts typically sync their history within a day. 9. What is Workspace MCP? It is the connection that lets you talk to your workspace from Claude or ChatGPT. You connect once, then ask questions, get reports, and request work in plain English. Changes that send to customers or affect money need your approval. The assistant never sees credentials or a raw database. Data and control 10. Who owns my data? You do. It lives in your workspace, it is not pooled with other businesses, and it is not used to train models for anyone else. If you leave, you can take it with you. 11. Can I export my data? Yes. Ask your operator for an export of any module or the whole workspace and you receive it in a standard format. You can also ask for specific records or the whole workspace to be deleted. 12. What can Orkie staff see? Operators work under named accounts with access limited to the modules in your engagement, and their actions are logged alongside your team's. They never see your passwords or connector credentials. Engineering staff do not browse workspaces. 13. How do approvals work? Reading data is instant. Small changes need a clear request. Actions that send to customers, move money, or push data to an ad platform need a person to approve the exact request, and deleting or merging customer records needs a second admin. This applies to your team, your agency, Orkie operators, and any AI assistant. 14. Is the pixel compliant with privacy rules? The pixel is first-party, honors your consent banner, records marketing permission only when a person opts in, and checks consent again before any automated message sends. Consent posture is visible by region in your workspace. Your legal team is welcome to review the details. Getting started 15. How do I talk to someone? Talk to us and pick a time. Bring a rough idea of where you sell, where you advertise, and the questions you cannot answer today. If you would rather start with a conversation, contact us.