# SegmentHub — full text > SegmentHub is a real-time customer data platform (CDP) and data management platform (DMP) that unifies anonymous and known visitor data across web, mobile, CRM and offline sources, segments visitors in milliseconds, and activates those segments across advertising and marketing channels. --- URL: https://www.segmenthub.com/about/ About SegmentHub Empowering businesses through data-driven personalization and real-time customer insights. ## Our Story Founded in Istanbul, Türkiye. SegmentHub was born from a simple yet powerful realization: businesses were drowning in customer data but starving for actionable insights. We recognized that traditional data platforms were either too complex, too slow, or unable to deliver the hyper-personalized experiences modern consumers expect. To solve this, we built a next-generation platform designed for agility and precision. Today, SegmentHub proudly serves leading retail, publishing, and e-commerce brands, helping them turn passive website visitors into highly engaged, loyal customers. ## Our Mission Our mission is to empower marketers and digital leaders with a privacy-first, real-time data ecosystem. We believe that delivering unparalleled customer experiences across digital touchpoints shouldn’t require an army of engineers. We aim to democratize advanced data management, making personalization seamless, scalable, and highly profitable. ## What We Do SegmentHub provides an all-in-one Customer Data Platform (CDP) and Data Management Platform (DMP) that unifies fragmented customer data into actionable, dynamic profiles. Our core solutions include: - Real-time Behavioral Tracking: Instantly understanding what users want based on micro-interactions. - Dynamic Segmentation: Creating incredibly precise audience cohorts without writing a single line of SQL. - Omnichannel Personalization: Delivering targeted smart banners, personalized search results, and context-driven content in milliseconds. ## Our Core Values Everything we build and every partnership we form is driven by four core principles: - Innovation at Speed: We believe in delivering technology that operates in real-time. Whether it's rendering a banner in under 100 milliseconds or rolling out new platform features, speed is in our DNA. - Privacy by Design: In a world of increasing data regulations, we ensure that our tools are built to protect end-user privacy while still delivering high-value marketing intelligence. - Customer Success: We don't just sell software; we partner with our clients. From major retailers to renowned publishers, your growth is the only metric that matters to us. - Simplicity: Complex data architectures are a reality, but the user interface shouldn't be. We design our platforms so that marketing teams can execute advanced strategies intuitively. ## Join Us on Our Journey We are always looking to partner with forward-thinking businesses and passionate individuals who want to redefine the future of customer data. Want to see what SegmentHub can do for your brand? Contact our team today or book a personalized demo. --- URL: https://www.segmenthub.com/ad-server/ First-Party Ad & Media Server Serve personalized ads. Bypass ad blockers. Host your own ad creatives and serve them directly from your domain using real-time CDP data. Zero third-party cookies, 100% visibility. Start Serving Ads Explore Documentation https://yourdomain.com Third-Party Ad Blocked 1st Party Ad Hey John, still interested? Complete your purchase today and get 20% off your abandoned cart items. { "segment": "cart_abandoner" } media.yourdomain.com/ad.jpg --- URL: https://www.segmenthub.com/alerts/ Alerts & integration health # The failures that look like success. A tag deployment drops the snippet and audiences quietly stop growing. An ad token expires and the ad set keeps spending against a customer list frozen the day it died. A relay password is rotated and the failed column climbs where nobody looks. Every one of these is invisible until somebody is told — so SegmentHub tells them. Book a DemoSee what it watches #martech-alerts CRITICAL · Ad activation failed Meta Ads — VIP Customers The network replied: token has expired. Last successful sync 3 days ago. WARNING · Ingest volume drop purchase — down 84% 61 events this hour against a median of 380 for Fridays at 14:00. RECOVERED · Email sending Relay accepting mail again One alert per problem ## Ingest volume drop An hour of event volume compared against what that hour is normally worth. Watch the whole account to catch a tag that stopped firing altogether, or name individual events to catch one broken integration among six. ## Ad activation failure The current state of every audience and ad network pair. A failed sync is critical and quotes what the network actually replied — normally the only thing that says what to fix. A high rejection rate is flagged too, because it usually means a format mismatch rather than an unmatchable list. ## Sender failure The failure rate of email, push and SMS sends since the last sweep — minutes, not a running daily average. Two million clean sends yesterday would bury four hundred consecutive failures this morning in a number nothing could move. ## A baseline that survives a normal week Being paged every weekend is how alerting gets switched off. The comparison is built to avoid that. ### The same hour, on the same weekday Traffic has a strong weekly shape. Comparing a Sunday morning against an average that is five-sevenths weekday invents a drop every weekend. The baseline is the median of that same hour on that same weekday over the previous four weeks. ### Median, not mean One week containing an outage or a Black Friday would drag an average far enough to either hide a real drop or invent one. A minimum-volume floor applies to the baseline, so an 80% fall on an hour that normally carries four events stays what it is: a quiet Tuesday. ### Zero is recorded as zero An hour in which nothing arrived is written down as an hour in which nothing arrived. Without that, a total outage and a quiet night look identical — and a total stop is the headline alert, the one that must never be the one that gets missed. ### Severity from your own threshold A 20% failure rate is critical to somebody who asked to hear about 10% and barely news to somebody who asked about 50%. Severity is measured against the number you set, and anything reaching total failure is always critical. ## One alert per broken thing A token that expired on Friday is one alert with a rising last-seen time and one notification — not eight hundred rows and eight hundred emails. ### Cooldowns and quiet hours A continuing problem refreshes its evidence silently and re-notifies only after the cooldown. Notifications inside quiet hours are held rather than dropped — and a recovery notice is never held. ### Recoveries announced When a sync succeeds or sending resumes, the alert closes itself and says so — but only if you were told about it in the first place. Telling somebody that a thing they never heard about has recovered is pure noise. ### "Not enough evidence" is a real answer A sync still running, or a channel that attempted nothing this sweep, is left exactly as it is. Treating that as healthy would close an open alert because the failing thing stopped being attempted — the most misleading possible moment to declare a recovery. ## Delivery that does not run through what it watches One of the things this module watches is whether your own message senders are working. Asking a relay that has started refusing mail to carry the message saying it has started refusing mail produces silence exactly when it matters most. Alert email leaves over the platform's own relay, never the bring-your-own relay your campaigns use. The webhook is a direct call, not a rule inside the webhooks module — an alert must not depend on the machinery it reports on. The payload is Slack-shaped by default, which Mattermost, Rocket.Chat and Google Chat all accept, with a plain JSON alternative for anything else. A notification that failed is retried, not swallowed, and the delivery error is shown on the alert — which is how somebody finds out their webhook has been returning errors for a month. Your webhook address is validated when it is saved and again when it is called, with redirects never followed. Alert history Meta Ads — VIP Customers Activation failure · opened 3d agoOpen purchase — ingest drop 84% below the Friday 14:00 medianOpen Email sending Resolved automatically after 41 minClosed Google Ads — Cart Abandoners 31% of records rejectedClosed Rules ship paused, so switching the module on never floods a new account. Illustrative interface values. ## Find out in minutes, not in the quarterly review. Alerting covers the whole platform — ad activations, email, push, SMS and the event stream that feeds all of them.Book a Demo --- URL: https://www.segmenthub.com/api-docs/ API Reference This document describes how to use the SegmentHub REST API to query and manage metadata about your visitors, ingest events, and activate segments in real-time. Overview Introduction & Auth Events Page View Product View Purchase Search Profiles Query Profile Update Attributes Update Segments Visitors Query Visitor Update Attributes Update Segments ## Description When you make a request to the REST API, you will specify an HTTP method and a path. Additionally, you might also specify request headers and path, query, or body parameters. The API will return the response status code, response headers, and potentially a response body. ### API Base URL The base URL for all API requests is: https://api.segmenthub.com ### Panel URL The panel address for any management needs where you can use to add/remove users, upload media, generate API Tokens, create reports, campaigns, or manage audiences: https://panel.segmenthub.com Authenticating & Tokens Many REST API operations are accessible without authentication. However, some operations require authentication or return additional information if you are authenticated. You can authenticate your request by adding a token. To own a token, please visit the panel and create an API Token by setting its access or limits. A token is required to directly modify a visitor or a profile data. About Modules - DMP: tracks all of your visitors' (devices) behaviours even if they are anonymous or not. - CDP: unifies multiple devices' behaviours of a known user. - Ad Server: returns campaigns by visitor interests to show best offers. ### API Response Codes This API uses the following error codes: - 200 OK: The request was succeeded. - 400 Bad Request: The request was malformed or missing required parameters. - 401 Unauthorized: The API token provided was invalid or missing. - 403 Forbidden: The client does not have access rights to the content. - 404 Not Found: The requested account not found or suspended. - 415 Unsupported Media Type: API is only willing to process application/json. - 500 Internal Server Error: An unexpected error occurred on the server. POST /campaigns/query ## Events - Page View Fires a page view event and returns eligible campaigns for the user. ### Body Parameters account Required The account uuid. visitorId Required The visitorId generated by the SDK (in the UUID4 format) of the visitor. profileId Optional The profileId (e-mail, phone, userId etc.) of the user. platform Required The platform code of your website or mobile app. Example: www.example.com device Optional The device type (desktop, tablet or mobile) of the current user. event Required The event type which is created in the Panel under the Events menu. path Optional The path of the current website or view name for the mobile apps. referrer Optional The referrer URL where visitor coming from. Request Body application/json { "account": "{{account}}", "visitorId": "{{visitorId}}", "profileId": "{{profileId}}", "platform": "{{platform}}", "device": "mobile", "event": "pageView", "path": "/", "referrer": null } Response 200 OK { "status": 200, "message": "Campaigns executed successfully.", "campaigns": [] } POST /campaigns/query ## Events - Product View Fires a product view event and returns eligible campaigns for the user. (Inherits common properties from Page View). ### Product Parameters sku Required The SKU information of the product being viewed. price Optional Price info of the product (US format locale). brand Optional The brand information of the product. breadcrumb Optional The breadcrumb (category path) information. category Optional The category information of the product. Request Body { "account": "{{account}}", "visitorId": "{{visitorId}}", "profileId": "{{profileId}}", "platform": "{{platform}}", "device": "mobile", "event": "productView", "path": "/", "referrer": null, "sku": "PRODUCT_SKU_HERE", "price": 99.90, "brand": "PRODUCT_BRAND_HERE", "breadcrumb": "PRODUCT_BREADCRUMB_HERE", "category": "PRODUCT_CATEGORY_HERE" } POST /campaigns/query ## Events - Purchase Fires a purchase event and returns eligible campaigns for the user. ### Purchase Parameters orderId Required The order id of the purchased items. orderTotal Optional Order total of the purchased items. purchasedItems Optional Array list of SKUs of the purchased items. Request Body { "account": "{{account}}", "visitorId": "{{visitorId}}", "profileId": "{{profileId}}", "platform": "{{platform}}", "device": "mobile", "event": "purchase", "path": "/", "referrer": null, "orderId": "ORDER_ID_HERE", "orderTotal": 199.90, "purchasedItems": ["SKU1_HERE", "SKU1_HERE"] } POST /campaigns/query ## Events - Search Fires a search event and returns eligible campaigns for the user. ### Search Parameters searchTerm Required The search term performed by the user. Request Body { "account": "{{account}}", "visitorId": "{{visitorId}}", "profileId": "{{profileId}}", "platform": "{{platform}}", "device": "mobile", "event": "search", "path": "/", "referrer": null, "searchTerm": "SEARCH_TERM_HERE" } POST /profiles/query ## Profiles - Query Returns requested attributes and segments of the given profile. ### Body Parameters account Required token Required The token generated from the Panel at the Account -> API Tokens page. profileId Required attributes Optional Array of attributes to request. Must be allowed for the given token. segments Optional Array of segments to request. Request Body { "account": "{{account}}", "token": "{{token}}", "profileId": "{{profileId}}", "attributes": [ "country", "firstName", "lastName", "lastViewedProducts" ], "segments": ["VIP", "Churn"] } Response 200 OK { "status": 200, "message": "Profile queried successfully.", "errors": [], "attributes": { "country": [{"value": "us"}], "firstName": [{"value": "John"}], "lastName": [{"value": "Doe"}], "lastViewedProducts": [ {"value": "SKU1"}, {"value": "SKU2"} ] }, "segments": ["VIP"] } POST /profiles/attributes ## Profiles - Update Attributes Updates requested attributes of the given profile. ### Body Parameters attributes Required Dictionary of attributes to update. Requested attributes must be allowed for the token. Request Body { "account": "{{account}}", "profileId": "{{profileId}}", "token": "{{token}}", "attributes": { "firstName": "Test", "lastName": "User", "email": "{{profileId}}" } } Response 200 OK { "status": 200, "profileId": "YOUR_PROFILE_ID", "message": "Profile attributes saved successfully.", "errors": [] } POST /profiles/segments ## Profiles - Update Segments Assigns or removes segments for the given profile. ### Body Parameters assignees Optional List of segments to assign to the profile. removes Optional List of segments to remove from the profile. Request Body { "account": "{{account}}", "profileId": "{{profileId}}", "token": "{{token}}", "assignees": [ "SEGMENT_TO_BE_ASSIGNED" ], "removes": [ "SEGMENT_TO_BE_REMOVED" ] } POST /visitors/query ## Visitors - Query Returns requested attributes and segments of the given visitor (anonymous user). Note: Requires visitorId instead of profileId. Request Body { "account": "{{account}}", "token": "{{token}}", "visitorId": "{{visitorId}}", "attributes": ["country"], "segments": ["VIP"] } POST /visitors/attributes ## Visitors - Update Attributes Updates requested attributes of the given visitor. Request Body { "account": "{{account}}", "visitorId": "{{visitorId}}", "token": "{{token}}", "attributes": { "gender": "Man", "favoriteBrands": ["Nike", "adidas"] } } POST /visitors/segments ## Visitors - Update Segments Assigns or removes segments for the given anonymous visitor. Request Body { "account": "{{account}}", "visitorId": "{{visitorId}}", "token": "{{token}}", "assignees": [ "SEGMENT_TO_BE_ASSIGNED" ], "removes": [ "SEGMENT_TO_BE_REMOVED" ] } --- URL: https://www.segmenthub.com/audience-intelligence/ Audience intelligence # Know who matches—and why—before you activate. Build real-time audiences with evidence. Preview unsaved rules, inspect masked matches, measure each rule's contribution and compare audience overlap before campaigns or destination syncs go live. Book a DemoRead the preview guide ## Preview before saving Run the rules still in the editor. See matched versus total profiles, calculation time and masked examples without publishing an audience first. ## Understand every rule Cumulative contribution counts show how the result changes as each condition is applied, making restrictive or ineffective rules easier to find. ## Compare overlap Measure intersection, exclusive membership and Jaccard overlap to understand duplicated reach before audiences compete for budget or attention. ## Audience QA built into the workflow ### Warnings before activation Identify zero-match, universal and extremely broad audiences before they reach a campaign or advertising account. ### Explain profile membership Open a profile and see which audience conditions included it—useful for campaign QA, support and privacy workflows. ### Rolling date audiences Use values such as today, one week ago or three months ago so recency audiences remain current without daily edits. Audience preview High-intent repeat visitorsLive 12,840 Matching profiles 18.6% Of all profiles Viewed product twice21,406 Seen within 2 weeks16,203 No purchase12,840 ## From question to activation A repeatable workflow for safer targeting. 01 ### Define Combine attributes, recency and included or excluded audiences. 02 ### Preview Check size, sample profiles, warnings and rule contribution. 03 ### Compare Measure overlap with audiences already in market. 04 ### Activate Use the verified audience on-site, in push or in ad networks. ## Stop guessing who your rules include. Preview and explain the audience before it controls a customer experience or media budget.See Audience Intelligence --- URL: https://www.segmenthub.com/careers/ Careers at SegmentHub Join us in building the future of real-time customer data management and omnichannel personalization. ## Why Join SegmentHub? At SegmentHub, we are building the next generation of real-time customer data management. Our platform helps leading retail, publishing, and e-commerce brands turn massive amounts of fragmented data into hyper-personalized, actionable experiences in milliseconds. We are a fast-growing, dynamic team based in Turkiye, driven by innovation, speed, and a passion for creating impactful technology. When you join SegmentHub, you are joining a culture that values autonomy, continuous learning, and big ideas. We embrace challenges and thrive on solving complex engineering and marketing problems for our clients. ## Perks & Benefits We believe that our team does their best work when they are supported both inside and outside the office. We offer: - Flexible Work Environment: Hybrid and remote-friendly options to fit your lifestyle and maximize your productivity. - Continuous Learning: Dedicated budgets for courses, conferences, and books to help you grow your skills. - Health & Wellness: Comprehensive private health insurance for you and your family. - Competitive Compensation: Rewarding salaries paired with performance-based bonuses. - Innovative Tech Stack: Work with the latest technologies in big data, real-time streaming, and cloud architecture. ## Open Roles We are rapidly expanding and always on the lookout for exceptional talent. While we frequently update our open positions, we are currently actively hiring for the following roles: - Senior Backend Engineer (Java/Python): Help scale our high-throughput data pipelines and ad servers to handle millions of requests per second. - Data Scientist: Develop predictive behavioral models, AI-driven recommendation engines, and real-time segmentation algorithms. - Customer Success Manager: Partner closely with enterprise clients to ensure they maximize their ROI and personalization strategies using SegmentHub. ## How to Apply Don't see a perfect match above? We still want to hear from you! If you are passionate about data, marketing technology, and building incredible products, we encourage you to reach out proactively. Please send your resume, portfolio (if applicable), and a brief introduction about why you'd be a great fit to careers@segmenthub.com. We look forward to meeting you! --- URL: https://www.segmenthub.com/case-studies/ Case studies What retailers and publishers actually did with real-time segmentation, and what it changed. Each study covers the problem, the setup and the measured outcome. +37% search-driven sales at Instreet 82% Google Ads customer match rate 10 ad networks kept in sync 3h audience refresh cycle Search personalization Instreet ## Personalized search results lift sales 37% A sportswear retailer reordered on-site search results against each visitor's live interest profile instead of showing everyone the same ranking. Read the study Paid media E-commerce ## An 82% customer match rate in Google Ads Syncing first-party audiences through Google Ads Data Manager to counter signal loss, with the feed rebuilt on a schedule so large audiences never time out. Read the study CRM enrichment Salesforce ## Enriching Salesforce with live behavioural data Static CRM records gained real-time behavioural context, so campaigns could react to what a contact did this morning rather than what they were last quarter. Read the study Mobile growth Sneaks Up ## Turning mobile web visitors into app installs High-intent mobile visitors were shown targeted install banners at the moment their behaviour said they were ready, instead of on every page. Read the study Ad revenue BeStyle ## Smart banners segmented by live visitor interest A retailer raised advertising revenue on its own inventory by matching each banner to the interests the visitor had shown in that session, served first-party from its own domain. Read the study --- URL: https://www.segmenthub.com/cdp-and-dmp/ Next-Gen CDP & DMP Turn fragmented data into a Single Source of Truth. Unify anonymous signals and known customer profiles in real-time. SegmentHub's hybrid CDP & DMP engine empowers you to build hyper-targeted audiences and activate them instantly. Request a Demo Explore Documentation Unified Profile App Events Anonymous ID: X891 POS Data Known User: John D. CRM Sync Email Engagement --- URL: https://www.segmenthub.com/consent-and-privacy/ Consent, DSAR & erasure # Prove it is actually gone. Most vendors will honour an erasure request. Almost none can tell you what happened to the copy in the profile store, the search index and the caches. SegmentHub owns every store it writes to, so an erasure reaches all of them in one pass and comes back with a signed receipt naming each one. Book a DemoRead the erasure guide Deletion receipt Signature verified Profile store shards8 of 8 Search indices2 of 2 Consent ledgerDeleted Suppression entryKept, hashed Audit trailRetained rcpt_9f4c2ae1…bd07 · signed Every store named ## Consent per purpose Analytics, advertising, personalization, email, SMS and push are decided separately, recorded with evidence, and enforced independently. Not one cookie banner checkbox standing in for six different lawful bases. ## Access on request One API call returns everything held about a data subject — the visitor record, the linked customer profile, every consent decision with its evidence, and their position on the suppression list. ## Erasure with a receipt Queued, audited, and fanned out across every store in the platform. The artefact that matters is not the API response — it is the signed receipt saying which stores were reached and when. ## Consent decides what is collected, not just what is sent A consent record that only gates the newsletter is a record that arrives too late. Enforcement can start at the moment an event is received. ### Off The default for every account. Nothing about your ingestion changes, and consent is recorded and reportable without gating anything until you decide otherwise. ### Pseudonymise The event still counts, but identifiers are stripped and the visitor id is replaced with a value that rotates daily. The day's events stay joinable to each other, and to nobody. ### Drop The event is discarded before it reaches any store. The tracking tag still receives a success response, because a tag told to retry would spend the day re-sending an event it is not allowed to send. ### Evidence, not a boolean Each decision is stored with its source, timestamp, the wording that was shown, the notice version and the originating address — kept in a durable ledger that outlives the behavioural profile it describes. "Never asked" is a distinct state from "said no", because treating them alike is how a platform ends up processing data nobody consented to. ### Biased towards not processing A newer decision wins, an older one never overwrites a newer one, and a withdrawal is never lifted by a grant arriving from a bulk import or an inference. Only a deliberate act — a consent management platform, an SDK call, a TCF string or a panel action — can re-grant. ## Where an erasure actually reaches A subject is a person, not a row. Erasing a visitor also erases the customer profile it is linked to, and erasing a profile reaches every visitor record pointing at it — because leaving half behind leaves somebody identifiable and re-linkable. ### Deleted - • Every visitor- and profile-shaped record across all profile-store shards - • Saved cart state and recent-activity membership - • Both search indices, refreshed immediately so the panel stops returning the subject - • The shared caches that hold "seen since the last cycle" - • The consent ledger rows for that subject ### Deliberately kept - • The suppression entry, anonymised. Deleting it would silently re-enable messaging that person the moment they were seen again — the opposite of what they asked for. - • The audit trail. Append-only, and the evidence of what the platform did, including this erasure. - • Your own event archive. It is your bucket under your retention policy, and the privacy report says so rather than implying otherwise. A partial erasure is reported, never retried quietly. A failure is terminal and surfaces with its reason, because an erasure that half-succeeded and re-ran forever is worse than one an operator was told about. Before each record goes, every purpose on it is written to denied — so a subject who is seen again starts from no permission rather than from whatever a stale integration last asserted. ## The privacy report is the answer to the questionnaire Every store named alongside what happens to it on erasure, so the security reviewer reads it instead of interviewing you. The consent position for the account: how many subjects granted, denied or were never asked, per purpose. Every receipt, re-verified on load. The report checks each signature rather than trusting a stored flag — a green tick that was never checked is worse than no tick at all. A declared data region per account for the residency conversation, alongside the single-tenant and on-premise deployment options already on the security page. IAB TCF v2.2 strings are read directly, so a consent management platform already on your site can drive all of this without a second integration. Consent by purpose Analytics92% granted Personalization78% granted Advertising61% granted Email44% granted SMS19% granted Consent is mirrored onto the profile as an ordinary attribute, so an audience can target "consented to advertising" through the normal rule builder. The gates themselves always read the record, never the mirror. Illustrative interface values. ## Turn the compliance conversation into a sales asset. Consent, access and erasure are built into the same platform that runs your profiles and activations — which is exactly why it can prove what happened.Walk through the privacy report --- URL: https://www.segmenthub.com/contact/ Get in Touch Whether you have a question about features, pricing, need a demo, or anything else, our team is ready to answer all your questions. ## Contact Information ### Email Us Our friendly team is here to help. hello@segmenthub.com ### Visit Us Come say hello at our office HQ. Nisbetiye mah. Gazi Gucnar sok. No:4/5, 34340 Besiktas/Istanbul, Turkiye ### Call Us Mon-Fri from 9am to 6pm. +90 (850) 888 56 32 Trusted by modern data teams Champion Sneaks Up Sportime Sending your message... Full Name * Work Email * Company Name How can we help you? I agree to the Privacy Policy and consent to have my data processed to respond to this inquiry. We couldn't send your message just now. Please try again, or email us directly at hello@segmenthub.com — the link opens an email with your message already in it. Send Message --- URL: https://www.segmenthub.com/cookies/ Cookie Settings Manage your data collection preferences. SegmentHub uses cookies and similar technologies to ensure our website works properly, personalize your experience, analyze our traffic, and for advertising purposes. You have the right to choose whether or not to accept certain types of cookies. Use the toggles below to adjust your preferences. Please note that blocking some types of cookies may impact your experience on our site and the services we are able to offer. For more detailed information, please read our Privacy Policy. ## Strictly Necessary Cookies These cookies are essential for the website to function securely and properly. They enable basic functions like page navigation, load balancing, and access to secure areas. The website cannot function optimally without these cookies. Always On ## Performance & Analytics These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us know which pages are the most and least popular and see how visitors move around the site. ## Functional Cookies These cookies enable the website to provide enhanced functionality and personalization. They may be set by us or by third-party providers whose services we have added to our pages. ## Targeting & Advertising These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. By clicking "Save Preferences", you consent to the cookie configurations you have selected above. Save Preferences Preferences Saved Your cookie settings have been successfully updated. --- URL: https://www.segmenthub.com/data-export/ Warehouse & storage export # Your data, in your own bucket. Every night SegmentHub writes events, profiles, visitors and campaign statistics to storage you own, in a format your warehouse loads without a conversion step. The bucket, the credentials, the storage bill and the retention policy are all yours — the same principle as bringing your own mail relay and your own ad credentials. Book a DemoRead the export guide s3://your-bucket/segmenthub/ acme/events/ dt=2026-09-05/ part-00001.parquet part-00002.parquet _load.sql _manifest.json dt=2026-09-06/ part-00001.parquet _manifest.json acme/profiles/ acme/email_campaign_stats/ Manifest = safe to load Re-runnable partitions ## Six datasets, every day Each with a fixed, published column contract — because once a partition is loaded, those names are in someone's models and dashboards. events by event time profiles by last seen visitors by last seen campaign_stats on-site email_campaign_stats daily rows push_campaign_stats daily rows Your own attribute names and event parameters travel in a JSON column rather than widening the table per account, so every tenant loads into the same fixed schema and a new attribute never breaks yesterday's model. ## Three formats, one layout your tools already understand ### Parquet Snappy-compressed columnar files with the best storage and scan economics. Arrays stay real arrays; JSON columns are strings your warehouse parses on read. ### NDJSON Gzipped, one object per line, with nested structure intact. Loads everywhere, and a human can decompress a part and read it — which matters more than it sounds at 3am. ### CSV Gzipped and flattened, for the spreadsheet and the legacy loader. Escaping is done properly, because attribute values routinely contain commas, quotes and newlines. ### Hive-style partitions Files land under dt=YYYY-MM-DD/, which BigQuery, Athena, Redshift Spectrum, Spark and DuckDB all discover as a partition column with no configuration. Data files start with part- and metadata with an underscore, so a wildcard load can never accidentally parse the manifest as data. ### The manifest is the commit marker Parts are written first and the manifest last, so "is this partition safe to load" is one cheap test. It carries the schema, per-file row counts, byte counts and checksums, and a line saying where the rows came from — which is the answer to the first question anyone asks about a light-looking day. ## A partition is a unit of work that can be redone The scheduled export, a ninety-day backfill, a retry after a bucket outage and a re-export you queue by hand are all the same code path reaching the same ledger row. That is why none of them can double a row in your warehouse. ### Backfill on request Events are re-read from the platform's own event archive rather than teed off the live stream, so any day the archive still holds can be exported today — and they are partitioned by when each event happened, not when it was archived. ### Replace, never append A re-run deletes the stale parts a shorter run leaves behind before it writes the manifest, so "replace the partition" is true rather than approximately true. Today is never exported: its partition is not closed yet. ### Never at the cost of the platform The sweep runs every fifteen minutes on its own worker pool with a per-account ceiling, so one tenant catching up on three months cannot slow the indexing your audience queries depend on. ## Into the warehouse, not just into a bucket BigQuery loads natively. Each day targets its own table partition and replaces it, so a retry corrects a day rather than doubling it. The schema is passed explicitly rather than auto-detected — a day where one column happened to be empty would otherwise land as a different type and break the loads weeks later. Snowflake, Athena and Trino get ready-to-run SQL. Every partition can carry a generated script with a COPY INTO, a LOAD DATA and a CREATE EXTERNAL TABLE, written from the same schema the files were written with, so the two cannot disagree. An existing table is left alone. You may have clustered it, added columns or set a retention policy, and none of that is ours to overwrite. The connection test writes and deletes a real object. It is the only honest check — a read-only key passes everything else and then fails at 03:00 on a partition nobody is watching. Partition ledger events · 2026-09-05Completed profiles · 2026-09-05Completed events · 2026-09-04Running visitors · 2026-09-04Queued events · 2026-09-03Retrying One row per dataset and day, not per attempt. A failed partition backs off and retries on its own; the panel can queue any date range for re-export. Illustrative interface values. ## Answer "can we get our data out?" with a bucket path. Pair it with the reporting module for day-to-day questions and the REST API for everything in between.Set up your first export --- URL: https://www.segmenthub.com/email-campaigns/ Email campaigns # One audience engine, now in the inbox. Send one-time, recurring and triggered email from your own SMTP server. The same real-time audiences that drive push and on-site personalization decide who receives each message, and recorded consent decides who never does. Book a DemoRead the deliverability guide Still thinking it over? shop@example.com · to you Return to your cart Unsubscribe · sent from your own domain Consent verified Audience matched ## One-time Send now or at a chosen moment to every consenting profile in one or more audiences. A completed send becomes read-only, so the same list is never mailed twice by accident. ## Recurring Run daily, weekly or monthly in the account's timezone. The audience is resolved again on every run, so a newsletter always reflects who qualifies today. ## Triggered Respond to a customer state such as an abandoned cart after the configured delay, minimum value and eligibility checks — reading the same cart signals mobile push uses. ## Write it once, and it arrives personally A block builder for marketers, a raw HTML mode for agency templates, and one rendering path shared by the preview, the test send and the real campaign. ### Template builder - • Drag-and-drop heading, text, image, button, divider, column, social and footer blocks - • Responsive, inline-styled HTML that survives older mail clients - • Raw HTML mode for templates built elsewhere - • Reusable account templates, snapshotted per campaign - • Subject and preheader written side by side ### Personalization and preview - • Placeholders resolved from any visitor attribute you already collect - • Fallback defaults for missing values, so nothing renders blank - • Cart variables for triggered sends: item count, total, first item name - • Desktop and mobile preview rendered against a real profile - • Send a test to yourself through the live pipeline ## Consent is the first filter, not the last Every campaign is checked against consent and a permanent suppression list — at targeting time and again at delivery, because people opt out in between. ### Consent on the profile Subscription state lives on the customer profile beside every other attribute, so audiences can target it directly and a reach estimate counts only mailable people. ### Permanent suppression Opt-outs, bounces and complaints are kept in a durable list that data-retention rules never expire, and an existing do-not-mail file can be imported on day one. ### One-click unsubscribe Standards-based one-click headers, plus an optional preference page hosted on your own domain so the opt-out experience never leaves your brand. Managing consent in the panel: search by address or profile, change a single customer with a recorded reason, bulk-update thousands of addresses at once, or upload a CSV suppression file. Every change is audited, and an unsubscribe applies to the very next send rather than the next indexing cycle. ## Your mail server, your sending reputation Bring your own relay: connect Amazon SES, SendGrid, Postmark, Mailgun or an in-house SMTP server. Mail leaves your own domain, so the deliverability you have built stays yours. Validated before it is saved: credentials are encrypted at rest, the connection is tested on save, and a deliverability checklist covers SPF, DKIM, DMARC and a monitored return path. Throttling that respects the relay: per-minute, per-hour and per-day limits, plus connection and messages-per-connection caps, enforced at send time across every worker. Quiet hours and UTM tagging: hold campaigns that fall outside the delivery window, and decorate every outbound link with the campaign's UTM parameters at render time. Campaign funnel Targeted48,220 Sent47,109 Opened16,942 Clicked4,851 Bounced, unsubscribed, complained and failed are reported alongside. Sent means accepted by your relay, never a guess at delivery. Illustrative interface values. ## Email that knows the rest of the journey. Reuse the audiences, cart signals and customer profiles you already have, and keep the inbox, mobile push and on-site personalization telling one story.Plan your first campaign --- URL: https://www.segmenthub.com/glossary/ Customer data glossary The vocabulary of customer data platforms, in plain language. One definition per term, with what it means in practice underneath. ## Customer Data Platform (CDP) A CDP is a system that builds one persistent, unified profile per customer from first-party data, and makes that profile available to other systems. It ties events to a known person using identifiers such as an email address, phone number or account ID, keeps that history for years, and is used for personalization, retention and omnichannel orchestration. The data comes from your own website, app, CRM and point-of-sale systems — never bought from a third party. ## Data Management Platform (DMP) A DMP collects and organizes anonymous audience data for advertising, then pushes it to ad platforms for targeting. It works with cookies, device IDs and IP addresses rather than personally identifiable information, and traditionally leaned on third-party data bought from data providers. Storage is short-term — typically around 90 days — because its job is capturing immediate intent for acquisition, not remembering a customer for years. Full comparison of DMP and CDP. ## Identity resolution Identity resolution is the process of deciding that activity seen on different devices or sessions belongs to the same person, and merging it into one profile. Deterministic resolution links records that share a confirmed identifier, such as the same logged-in email address. Done in real time, it is what lets a system know that the visitor browsing on a phone now is the one who abandoned a cart on a desktop yesterday. ## First-party data First-party data is information you collect directly from your own audience, with their consent. Website behaviour, purchase history, CRM interactions and survey responses all qualify. It is the foundation of privacy-safe targeting, because it does not depend on cross-site tracking or on data bought from anyone else. ## Anonymous visitor tracking Anonymous visitor tracking profiles the visitors who have not identified themselves, so they can be segmented before they ever log in or share an email address. Typically 97–98% of website visitors are anonymous; only 2–3% end up identifying themselves. Profiling the rest, and connecting their devices to profiles as evidence accumulates, reduces the share of traffic you know nothing about. ## Server-side tracking Server-side tracking moves data collection off the visitor's browser and onto your own server, which then forwards what you choose to third parties. It is more reliable than browser pixels, which ad blockers and browser privacy features increasingly block; it removes JavaScript from the page, which helps Core Web Vitals; and it puts you in control of exactly what leaves for each destination. ## Customer match Customer match is the mechanism ad networks use to find their own users from a list of hashed identifiers you upload. You send SHA-256 hashes of normalized email addresses rather than raw ones, so the network can compare without either side exchanging plain contact details. Every network sets a minimum number of matched users before the resulting audience can be targeted, and matching is asynchronous — the matched size appears hours or days later. See the thresholds per network. ## Match rate Match rate is the share of the identifiers you upload that an ad network recognises as its own users. It is capped by how many of your customers use that network with the same email address. Sending identifiers a network cannot match — phone numbers to a destination that only accepts hashed email, for instance — only depresses the number. ## Real-time segmentation Real-time segmentation evaluates a visitor's membership of an audience as they act, rather than in a nightly batch. The distinction matters when the response has to happen inside the same session: a banner, a reordered search result or a personalized offer is useful now and worthless tomorrow morning. ## Computed traits Computed traits are profile attributes derived from raw events rather than collected directly. Lifetime order value, most-viewed category or days since last purchase are all computed: nobody submits them in a form, the platform maintains them as events arrive so that segments can be built on them. ## Data replay Data replay re-processes historical events through current logic, so a new segment is populated with people who already qualified in the past. Without it, a segment created today starts empty and only fills as new activity arrives, which can mean waiting weeks before it is large enough to use. ## On-site messages On-site messages are creatives shown on your own website while the visitor is there: popups, fullscreen takeovers, slide-ins, announcement bars and inline banners. Unlike an ad, they need no third party and no bought inventory, and the overlays need no container in the page — they appear over it. Their value comes from targeting: the same offer shown to everyone is noise, while one shown to the right segment at the right moment is service. In SegmentHub they are designed from a gallery of templates and targeted like any other campaign. See On-site Marketing. ## Exit intent Exit intent is the signal that a visitor is about to leave a page, used to show a message at the last useful moment. On a desktop it is detected when the pointer leaves the page through the top of the window, towards the tabs and the address bar. Touch screens have no pointer, so there it is approximated: a quick upward scroll, or a fallback delay. It is one of several display triggers, next to a delay, a scroll depth and inactivity. Display triggers in SegmentHub. ## Lead capture Lead capture is collecting a visitor's contact details — usually an email address or phone number — through a form, typically in exchange for an offer. What matters is where the answer goes. In SegmentHub a form in a popup writes each field to the visitor's own profile, and a ticked consent box is recorded together with the wording the visitor agreed to. An address on its own is not permission to send, and an earlier opt-out is not lifted by a new signup. Lead capture forms. ## Spin-to-win Spin-to-win is a gamified popup in which the visitor spins a wheel, or scratches a card, to reveal a prize such as a discount code. It is often placed behind an email field, which makes it a lead capture form with a reason to fill it in. For the prizes to be real, the draw has to be made on the server: the browser should know only the names on the wheel, never the odds or the codes, and a visitor should get one play. Games in SegmentHub. ## Where these show up in the product Identity resolution, computed traits, real-time segmentation and data replay are all part of the CDP & DMP. Customer match and match rate belong to audience activation. Server-side delivery is what the first-party ad server is built on. On-site messages, exit intent, lead capture and spin-to-win are part of On-site Marketing. --- URL: https://www.segmenthub.com/ Coming soon: Social Intent Engine — turn social engagement signals into actionable audiences Unify Data. Personalize Experiences. The real-time Customer Data Platform (CDP) and Data Management Platform (DMP) that turns anonymous traffic into loyal customers through instant segmentation. Request a Demo Total Visitors 1,240,592 +12.5% Segmented Users 892,101 Real-time Events 4,200/s Trusted by data-driven companies Champion Columbia Desa Etstur Flying Tiger Instreet İlaçsız Yaşam Sneaks Up Sportime The Moose Bay Champion Columbia Desa Etstur Flying Tiger Instreet İlaçsız Yaşam Sneaks Up Sportime The Moose Bay ## Complete Data Ecosystem Everything you need to collect, organize, and activate your customer data. ### Ad Server Serve personalized ads and banners on your own platforms using first-party data. Bypass ad blockers with server-side delivery. View Ad Server ### Alerts & Health Be told when ingestion drops, an ad token expires or a sender starts refusing — one alert per broken thing, delivered to email and Slack. See Alerts ### Audience Intelligence Preview unsaved rules, inspect masked sample profiles and compare audience overlap before a segment reaches a campaign or ad network. See Audience Intelligence ### CDP & DMP Unify anonymous and known user profiles. Track 100% of traffic and segment audiences in real-time based on behavior. Explore CDP ### Consent & Privacy Purpose-scoped consent, TCF v2.2 support, subject access exports and erasure that reaches every store and returns a signed receipt. See Consent & Privacy ### Email Campaigns Personalized, consent-checked email sent from your own SMTP server to the same real-time audiences, with a template builder and full funnel reporting. See Email Campaigns ### On-site Marketing Popups, announcement bars, slide-ins and banners from a gallery of 26 templates, shown to the right segment on scroll, exit intent or inactivity — with signup forms, coupons and games. See On-site Marketing ### Push Notifications One-time, recurring and triggered notifications for your app and the browser, driven by live audiences, with quiet hours, frequency caps and deep links. See Push Notifications ### Reporting Saved reports, dashboards and exports over the same live profile data, so the number in a review is the number the campaign targeted. See Reporting ### SMS & WhatsApp Audience-targeted messaging through your own Twilio, MessageBird or Vonage account, with the billable cost shown before you send and one STOP silencing both channels. See SMS & WhatsApp ### Warehouse Export Daily partitioned Parquet, NDJSON or CSV written to your own S3 or Google Cloud Storage bucket, with native BigQuery loads and generated Snowflake and Athena SQL. See Warehouse Export ### Web Push Reach the visitors who never installed an app. Browser notifications on your own VAPID keys, sharing the audiences and delivery policy of every other channel. See Web Push ## Real-time actions, not just reports. ### Instant Segmentation Don't wait for batch processing. Move users into segments the millisecond they perform an action. ### Privacy First Fully GDPR & CCPA compliant. On-premise installation options available for total data sovereignty. ### Omnichannel View Connect Web, Mobile, CRM, and Offline data to create a single, unified 360-degree customer profile. ### On-site Messages Show popups, announcement bars, slide-ins and banners to the segment you choose — on scroll, exit intent or inactivity — with signup forms that write to the profile, coupons and spin-to-win games. Explore on-site marketing ### Advertising Audience Sync Keep verified audiences refreshed across nine advertising networks on their configured schedules, using normalized SHA-256 identifiers and auditable activation runs. Explore ad network integrations SegmentHub Core Engine Store Website Mobile App On-site Messaging Ad networks ## Seamless Integrations Connect SegmentHub with your favorite tools. We support 50+ one-click integrations for data ingestion and activation. ## Latest Insights Trends in personalization, data privacy, and growth marketing. View all posts Update Oct 18, 2026 • 6 min read ### On-site Popups Without Code Popups, bars, slide-ins and banners from a gallery of 26 templates, adjusted per device, shown by trigger and measured in SegmentHub and GA4. ST SegmentHub Team Tech Sep 6, 2026 • 6 min read ### What an SMS Campaign Actually Costs One pasted character can triple the bill, one STOP has to silence every channel reaching that number, and a badly stored phone number reads as reachable forever. ST SegmentHub Team Strategy Sep 3, 2026 • 5 min read ### Deleting Is Easy. Proving It Is the Hard Part What a defensible right-to-erasure actually reaches, what it keeps on purpose, and why the signed receipt matters more than the API response. ST SegmentHub Team View all posts ## Frequently Asked Questions Everything you need to know about SegmentHub. ### What is the main difference between SegmentHub and a traditional DMP? Traditional DMPs rely on batch processing and often use 3rd party data which is becoming obsolete. SegmentHub is a real-time CDP that focuses on 1st party data, allowing you to segment and act on visitor behavior the instant it happens, not 24 hours later. ### What is the value of Anonymous Visitor Tracking? Typically, 97% or 98% of website visitors are anonymous. For most companies, only 2%-3% of visitors end up sharing their email address or otherwise identifying themselves. - Anonymous Tracking profiles anonymous visitors, connects their devices to profiles and reduces the number of truly unknown users. - Segments all your visitors in real-time, creates segments, and offers relevant campaigns or personalizes/optimizes content. - Drives better engagement and ROI by matching campaigns or content to visitors. - Deliver a personal experience by providing a great moment to move a visitor forward in the buyer journey by offering targeted but more advanced content. ### Is SegmentHub GDPR and CCPA compliant? Yes. Consent is recorded per purpose — analytics, advertising, personalization, email, SMS and push are decided separately — and can gate collection itself, not just messaging. A right-to-erasure request reaches every store the platform owns in one pass and returns a signed deletion receipt naming each one. IAB TCF v2.2 strings are read directly, and on-premise deployment is available for strict data sovereignty requirements. See Consent & Privacy. ### Can I integrate SegmentHub with my existing CRM? Yes. We have native bi-directional integrations with Salesforce, HubSpot, Microsoft Dynamics, and Zoho. You can enrich your CRM contacts with web behavior data and use CRM attributes to personalize the web experience. ### Is there an API? Yes, we have an API which is documented and can be accessible from the Panel. We also provide SDKs for web and mobile platforms. ### Are there any commitments or contracts? There are no commitments or contracts. SegmentHub is a month-to-month service you can cancel your subscription at any time. ## Ready to own your customer data? Join growing companies using SegmentHub to drive growth through personalization. Plans start at $2,500 per month. Browse Use Cases Talk to Sales --- URL: https://www.segmenthub.com/integrations/ Audience activation Your segments, everywhere you advertise. SegmentHub keeps audiences in sync with ten advertising networks. Build a segment once and it is pushed to every connected destination on a schedule, as normalized SHA-256 hashed identifiers — raw email addresses never leave your account. ## Refreshed every three hours Every connected network is rebuilt on a three-hour cycle, so an audience a visitor qualifies for this morning is targetable the same day. Yandex is the exception and runs once a day, because it locks a segment for around two hours after each upload. ## Hashed before it leaves Identifiers are normalized and hashed with SHA-256 before upload, which is what every network's customer-match programme expects. Only profiles carrying the identifier a network can match are included, so nothing is sent that could never match. ## Every run is auditable The panel records each synchronization: audience size, eligible records, how many were added, removed or rejected, the duration, and the error returned if a run failed. When a network stops accepting an audience, you can see exactly when and why. ## Advertising networks Each network has its own minimum audience size and matching behaviour. These are the ones that matter in practice. Network Destination Sync Minimum to target Google Ads Customer Match list via Data Manager HTTPS feed, rebuilt every 3h Google's own thresholds apply Meta Custom Audience API push every 3h Meta's own thresholds apply LinkedIn DMP segment API push every 3h Matched asynchronously Microsoft Advertising Customer list Full rewrite every 3h 300 matched people TikTok Customer File audience File replaced every 3h ~1,000 matched users X (Twitter) Custom audience API push every 3h 100 recently active users Pinterest Customer list audience API push every 3h 100 matched accounts Reddit Custom audience Delta sync every 3h ~1,000 matched redditors Yandex Yandex Audience segment Once a day 100 email identifiers OpenAI Custom audience, CSV export Manual upload — no audience API yet 25,000 matched users Delta sync means only what changed is sent: profiles that join the audience are added and those that leave it are removed, so a list never drifts out of step with the segment behind it. ## The parts that usually go wrong ### Tokens that expire quietly LinkedIn, Pinterest, Reddit, Microsoft and Yandex all mint a short-lived access token from a refresh token. SegmentHub refreshes them on every run, so a connection does not silently stop working weeks later when a token expires. ### Large audiences and feed timeouts The Google Ads feed is regenerated on a schedule and served from cache, so Google gets it instantly regardless of how large the audience is, instead of waiting on a query that might time out. ### Identifiers a network cannot match Reddit and Yandex match on hashed email only. Profiles identified by phone number are left out of those uploads rather than padded in, because that column could never match and would only depress the reported rate. ### Stable segment IDs Yandex and Reddit audiences are created once and then refreshed in place, so the ID you target in a campaign never changes underneath you. ## Data sources and destinations Beyond advertising, SegmentHub connects to the tools your data already lives in. Salesforce HubSpot Microsoft Dynamics Zoho Google Analytics 4 Firebase BigQuery Power BI Mailchimp Slack Hadoop / Spark REST API & SDKs Twilio MessageBird Vonage WhatsApp Business Amazon S3 Google Cloud Storage Snowflake Athena / Trino SMTP relays Web Push (VAPID) IAB TCF v2.2 Outbound webhooks ### Messaging gateways SMS and WhatsApp go out through your own Twilio, MessageBird or Vonage account, so the sender registration, the country routing and the rate card stay yours. See the module. ### Storage and warehouses Daily partitioned Parquet, NDJSON or CSV lands in your own S3 or GCS bucket, with native BigQuery loads and generated SQL for Snowflake, Athena and Trino. See the module. ### Alert destinations Integration-health alerts arrive by email and over a Slack-compatible webhook that Mattermost, Rocket.Chat and Google Chat also accept, with plain JSON for anything else. See the module. Anything not listed can be reached through the REST API. ## Integration questions ### How often are audiences synced to ad networks? Every three hours for Google Ads, Meta, LinkedIn, Microsoft Advertising, TikTok, X, Pinterest and Reddit. Yandex syncs once a day, because Yandex locks a segment for around two hours after each upload while it recalculates and limits how often that can happen. ### Do raw email addresses leave my account? No. Identifiers are normalized and hashed with SHA-256 before anything is uploaded, which is the format every network's customer-match programme expects. ### Can I sync an audience to OpenAI Ads Manager? Not automatically. OpenAI does not publish an audience API yet, so SegmentHub exports the audience as a CSV of SHA-256 hashed email addresses that you upload in Ads Manager. OpenAI requires at least 25,000 matched users after its own matching before an audience becomes usable. If OpenAI ships an audience endpoint, this becomes a scheduled sync like the other networks. ### Why is my audience not targetable yet? Every network sets a minimum matched size before a list can be used: around 100 for X and Pinterest, around 1,000 for TikTok and Reddit, 300 for Microsoft Advertising and 25,000 for OpenAI. The list is still uploaded below that threshold and becomes targetable on its own once the audience grows. Matching is asynchronous, so Microsoft for instance reports a matched size only after about 48 hours. ### Why do I have to bring my own SMTP, gateway and bucket? Because the things that matter most on those channels are yours, not ours. Email sent through your own relay carries your sending reputation rather than a shared pool's. SMS sent through your own Twilio, MessageBird or Vonage account is billed at your rate card and routed by your own rules, with no reseller margin in between. Data written to your own S3 or Google Cloud Storage bucket stays under your retention policy and your residency commitments. It also means there is no second copy of your customer data sitting in a vendor's account. ### How do I find out when an integration breaks? You are told. An expired ad-network token, an audience whose records are being rejected in unusual numbers, a relay or gateway that has started refusing sends, and a drop in event volume against the same hour on the same weekday all raise an alert — one per broken thing, delivered by email and to a Slack-compatible webhook, and closed automatically with a recovery notice when the problem clears. See Alerts & Health. --- URL: https://www.segmenthub.com/media-server/ Media Server Show the right campaign to the right visitor. The Media Server is the delivery layer for every on-site campaign. It picks the campaign each visitor qualifies for, in real time, and renders it on your own site — a popup, an announcement bar, a slide-in or an inline banner from the Gallery — through the SegmentHub tag you already have installed. See On-site Marketing Book a Demo mystore.com Welcome back, Ada! 20% off your favourite sneakers. Claim Offer inline slot segment: "VIP" slot: "Announcement bar" frequency: "counted on view" --- URL: https://www.segmenthub.com/mobile-push/ Push notifications # Push at the right moment, not every moment. Use real-time audiences to send one-time, recurring and triggered notifications to your mobile app and to the browser. Respect quiet hours and frequency limits while deep links take each customer to the next useful action. Book a DemoRead the cart recovery guide Your cart is waiting Complete your order while your items are still available. Quiet hours respected Audience matched ## One-time Schedule a launch, service message or limited campaign for every reachable profile in one or more audiences. ## Recurring Run daily, weekly or monthly in the account's timezone while the audience is resolved again for each send. ## Triggered Respond to a customer state such as an abandoned cart after the configured delay and eligibility checks. ## Cart recovery with customer context A reminder is sent only after the shopper, cart and timing rules agree. ### Qualification controls - • Configurable delay after cart activity - • Minimum cart value - • Audience eligibility - • Per-customer reminder frequency - • Quiet hours in the account timezone ### Useful message context - • Item count, cart total and first item name - • Images, sounds and app deep links - • Custom data payloads - • TTL and collapse-key controls - • Android notification channel ## Two transports, one module Most of your audience will never install an app. Web push reaches them in the browser, and it is not a separate product with separate rules — the campaigns, the audiences, the delivery policy and the reports are the same ones. ### Mobile push - • Your own Firebase project, credentials encrypted at rest - • iOS and Android, with an Android notification channel - • App deep links, sounds and custom data payloads - • Invalid tokens pruned automatically after a send ### Web push - • Your own VAPID key pair, generated in the panel or pasted in - • Chrome, Edge, Firefox, Opera, Samsung Internet and Safari - • A service worker snippet with your account details filled in - • No app, no SDK and no store reviewExplore web push One person, one message. Frequency caps and quiet hours are counted per customer, so a phone and a browser share a single budget rather than doubling it. A campaign can name the platforms it was written for, and the filter is applied before the newest-device pick — so a browser-only campaign finds a person's newest browser instead of skipping them because their newest device is a phone. ## Delivery controls that protect the experience Frequency caps: limit non-triggered pushes per profile per day. Fresh-device selection: choose a recently active device and deduplicate shared tokens. Reliable batching: divide sends into provider-safe jobs, retry transient failures and remove invalid tokens. Reporting: track targeted, sent, delivered, failed and invalid-token outcomes by campaign and day. Campaign delivery Targeted24,810 Sent23,965 Provider accepted23,702 Illustrative interface values ## Make push part of the customer journey. Coordinate real-time audience data, respectful delivery controls and measurable outcomes in one platform.Plan your first campaign --- URL: https://www.segmenthub.com/on-site-marketing/ On-site Marketing Popups that know who is looking. Pick a popup, slide-in, announcement bar or banner from a gallery of ready-made templates, make it yours, and show it to the segment you choose — on exit intent, after a scroll or a pause. Signup forms, coupons and spin-to-win games included, with no new code on your site. Request a Demo Read the launch article mystore.com/knitwear Free shipping this weekend · ends in 02:14:37 Hi Ada, 20% off knitwear 02hrs 14min 37sec AUTUMN20 Copy Shop now Just for you segment: "Knitwear browsers" trigger: exit_intent ## Start from the Gallery, not from a blank page 26 built-in templates in five kinds, for promotions, countdowns, announcements, coupons, signups and games. Change the words, images, colours and buttons in a form with a live preview, and save the result as one of your designs. ### Popup A centred window over a dimmed page, with a teaser tab before it opens or after it closes. ### Fullscreen A takeover that covers the screen, for the offer that deserves the whole stage. ### Slide-in A card from a corner or a drawer from the edge. The page stays usable underneath. ### Announcement bar Over the page, pushing it down, or inside your header — staying, scrolling away or sticking as the visitor scrolls. ### Inline banner Inside the page, where you point it. Several banners in one campaign rotate as a carousel. ### One design, three layouts Adjust the tablet and mobile layout of a design — sizes, position, hidden blocks — or switch it off on a device class. The layout follows the screen width, and the preview switches between all three. ### Your brand from the start A brand kit sets your colours, corner radius, font and logo on every template you open. Images come from your own media library. ### Templates of your own Save a finished design as a private template for the whole team. A design is shared by every campaign that uses it, so a fixed typo is fixed everywhere — the editor tells you how many campaigns that is first. ## More than an image and a link Headlines, text, images and buttons are the start. A design can also count down, hand out a code, collect a signup, greet a known visitor and show the products picked for them. ### Countdowns To a fixed moment, to the campaign's end date, or an evergreen timer that starts at each visitor's first view. When it runs out, hide the timer, hide the design or show a closing line. ### Coupons One code for everybody with a copy button, or a unique code for each winner from a coupon pool you upload — every code handed out once and never again. ### Signup forms Email, phone and name fields with email and SMS consent boxes. After a submission, show a thank-you, reveal a coupon, send the visitor to a page or close. ### A greeting by name Put a visitor's own value into a headline, text or button, with a fallback for everybody else: {$firstName|there}. Values are filled in and escaped on the server, so the browser gets a finished design. ### Products picked for them A row of up to 12 products from the recommendation engine — picked for this visitor, from a category, or what they looked at last — and when there is nothing to show, you choose whether the block or the whole design steps aside. ### Spin-to-win and scratch cards A wheel of 2 to 12 slices or a scratch card, on its own or behind an email box. Each prize can be nothing, a prize, one code or a unique code from a pool. ## The right moment, for the right people A design is shown by a campaign, so everything a campaign already does applies: segments, visitor attributes, events and their parameters, platforms, start and end dates, priority and variations. A display trigger decides the moment. ### Immediately or after a delay A delay only counts while the tab is visible, so nobody comes back to a popup that opened in the background. ### At a scroll depth Once the visitor has read far enough down the page to be interested. ### On exit intent When the pointer heads for the tabs and the address bar. Touch screens have no pointer, so there it opens on a fast scroll up or after a fallback delay you set. ### After inactivity When the visitor has not moved, typed, scrolled or tapped for the time you choose. ### Never one popup too many One at a time. Each placement shows one campaign, chosen by priority, so two popups never open together — while a popup and a bar can. Add a second bar placement to run a top and a bottom bar side by side. Capped when seen, not when sent. The campaign's frequency cap is counted when the design is actually on screen, so a popup waiting for exit intent that never came does not use it up. Respect a no. Stop showing a design for a number of days after the visitor closes it, clicks it or sends its form. Once per page view. A design already shown is not shown again on the same page, even when the page asks for campaigns twice or a second tab opens. ## Lead capture that keeps the evidence - Each field is written to the visitor attribute you map it to; phone numbers are normalised to E.164 with your default country. - A ticked consent box becomes an email or SMS subscription, with the box's own wording kept as evidence. No box, no consent: an address is not permission. - Somebody who opted out earlier stays opted out, whatever they submit later. - Bots are turned away quietly: a hidden honeypot field, a minimum time to fill the form, and one accepted submission per visitor per campaign every ten minutes. - Only the fields the design declares are accepted, and the values stay on the profile — never in the event archive or in GA4. - Optionally, a submitted email address identifies the visitor as that profile, for accounts that use the email as their profile id. ## Games that can't be gamed - The prize is drawn on SegmentHub's servers, by the odds you set. The browser only gets the slices' names and colours — never the odds or the codes. - One play per visitor, and behind a form one per email address. Playing again shows the first result. - A unique code from a pool is claimed by exactly one winner; the panel shows how many codes are left, not the codes. - A daily limit per pool caps what can be handed out in a day. - Plays are counted on the design's report and become an event with the prize and whether the visitor won. ## Every view, click and close — counted once, used everywhere In the campaign report: views, clicks, closes and form submissions per variation, beside every other campaign. A view means at least half of the design was on screen for a second. Per design: one report across all the campaigns that use a design, by day, by layout and by campaign — including teaser opens and games played. As events in SegmentHub: onsite_view, onsite_open, onsite_click, onsite_cancel, onsite_submit and onsite_play drive segments and event actions like any other event — “everyone who closed the autumn popup” is one rule. Each can be switched off. In Google Analytics 4: through the gtag() or GTM dataLayer already on your site, so Consent Mode stays in charge. The names are yours to change, and the whole thing can be switched off. Submitted values and profile ids are never sent. GA4 events, by default viewview_promotion teaser openedopen_promotion clickselect_promotion closeclose_promotion form sentgenerate_lead With promotion_id, promotion_name, creative_name and creative_slot, so GA4's standard promotion reports work without setup; clicks add click_url and closes close_method. ## Nothing to install, nothing to break The SegmentHub tag already on your site does the work. It runs SegmentHub's code inside your pages, so it was built with the same care as your checkout. ### No new snippet The existing tag loads the on-site script only on a page where a gallery campaign is served. Every other page pays nothing. ### Isolated from your styles Each design renders in its own Shadow DOM: your theme's CSS can't break it and its CSS can't leak into your page. ### Data, not HTML A design is a set of typed blocks, inserted as text. Links are http, https, mailto or tel only, so nobody can put a script on your site through the Gallery. ### No layout shift Images are decoded before a design appears, and a bar that pushes the page reserves its space first. No web fonts and no third-party requests are added. ### Accessible by default Labelled dialogs, focus kept inside and returned on close, Escape to dismiss, a teaser that is a real button, reduced motion and right-to-left pages respected. The editor warns when colours fall below WCAG AA contrast. ### Preview on your own site A preview link shows a design on your real pages before any campaign does, clearly marked as a preview. A design targeted on visitor data is only shown to visitors who allowed personalization — see Consent & Privacy. Placements, carousels and campaign delivery are on the Media Server page; the segments come from the CDP & DMP. ## On-site marketing questions ### Do I need to add anything to my website? No. The SegmentHub tag that is already on your site recognises gallery campaigns and loads the on-site script on the pages where one is served. Popups, slide-ins and bars need no container on the page; an inline banner goes where its placement's CSS selector points. ### Can a popup and a bar show at the same time? Yes. Each placement shows one campaign at a time, chosen by priority. The popup placement never opens two popups together, but a popup and an announcement bar sit in different placements and can appear side by side. ### What happens to my existing image and HTML campaigns? They keep running. An image variation can be turned into a gallery design with one click, Convert to Gallery. Custom HTML stays available as an advanced option, created and edited by platform administrators, because it runs script on your site. ### Does it work in Google Tag Manager-only setups? Yes. When the page has a gtag() function the GA4 events go through it; otherwise they are pushed to the GTM dataLayer, where a GA4 event tag listening for the names forwards them. SegmentHub never loads Google's library itself and never holds your measurement id. ## Your next popup is already in the Gallery. Pick a template, aim it at a live segment and see it on your own pages today — with the numbers in your campaign report and in GA4. Request a Demo --- URL: https://www.segmenthub.com/posts/ # Latest Insights Deep dives into data personalization, customer journey mapping, and the future of digital advertising. All Posts Strategy Technology Use Cases Updates Update Oct 18, 2026 • 6 min read ## On-site Popups Without Code Popups, bars, slide-ins and banners from a gallery of 26 templates, adjusted per device, shown by trigger and measured in SegmentHub and GA4. ST SegmentHub Team Tech Sep 6, 2026 • 6 min read ## What an SMS Campaign Actually Costs One pasted character can triple the bill, one STOP has to silence every channel reaching that number, and a badly stored phone number reads as reachable forever. ST SegmentHub Team Strategy Sep 3, 2026 • 5 min read ## Deleting Is Easy. Proving It Is the Hard Part What a defensible right-to-erasure actually reaches, what it keeps on purpose, and why the signed receipt matters more than the API response. ST SegmentHub Team Tech Sep 2, 2026 • 3 min read ## Email Consent, Suppression and Deliverability Why an opt-out cannot expire with behavioral data, and what protects a sending domain before the first campaign goes out. ST SegmentHub Team Tech Aug 31, 2026 • 6 min read ## Exporting to the Warehouse Without Duplicating Rows Why a nightly export job is the wrong shape, and how a partition ledger makes the backfill, the retry and the scheduled run one code path. ST SegmentHub Team Tech Aug 24, 2026 • 2 min read ## Audience Preview Before You Publish Validate audience size, inspect masked matching profiles and understand every rule's contribution before activation. ST SegmentHub Team Strategy Aug 10, 2026 • 2 min read ## Audience Overlap and Campaign Cannibalization Use intersection, exclusive membership and proportional overlap to prevent duplicated reach and conflicting messages. ST SegmentHub Team Use Case Jul 27, 2026 • 2 min read ## Mobile Push and Audience-Aware Cart Recovery Combine cart state, audience eligibility, quiet hours and frequency limits for more respectful recovery messages. ST SegmentHub Team Use Case Feb 2, 2026 • 3 min read ## Intent-Based Homepage Personalization for İlaçsız Yaşam How SegmentHub reordered, displayed, and suppressed homepage slides to match each visitor's membership, purchase, profile, and loyalty journey. ST SegmentHub Team Use Case Feb 5, 2025 • 3 min read ## Personalized Search Results Learn how Instreet leveraged SegmentHub to increase search-driven sales by 37% through real-time personalized search results. ST SegmentHub Team Use Case Jan 15, 2025 • 3 min read ## Segmented Smart Banners Learn how BeStyle leveraged SegmentHub to enhance its advertising revenue by delivering personalized smart banners based on real-time visitor interests. ST SegmentHub Team Use Case Dec 10, 2024 • 3 min read ## Targeted App Install Campaigns: Driving Mobile Adoption for Sneaks Up Increase mobile application installations and foster higher user engagement by capturing the attention of high-intent mobile web visitors through intelligent, personalized banner placements. ST SegmentHub Team Tech Dec 5, 2024 • 3 min read ## DMP vs CDP: Which Do You Really Need? Confused by the acronyms? We break down the technical differences between Data Management Platforms and Customer Data Platforms and why a hybrid approach is winning. ST SegmentHub Team Use Case Nov 14, 2024 • 3 min read ## CRM & CDP Behavioral Data Enrichment: Powering Salesforce with Real-Time Insights Improve the effectiveness of marketing campaigns by overcoming static data limitations and leveraging real-time behavioral insights to enrich their existing Customer Relationship Management (CRM) workflows. ST SegmentHub Team Strategy Oct 24, 2024 • 3 min read ## The Future of Cookie-less Tracking Chrome kept third-party cookies after all. Here is why signal loss arrived anyway, and what a first-party data strategy has to cover now. ST SegmentHub Team Use Case Jun 4, 2024 • 3 min read ## Google Ads Data Manager: Achieving an 82% Customer Match Rate with Custom Audience Sync Enhance targeted advertising by leveraging advanced audience segmentation and synchronization capabilities to combat signal loss and drive campaign efficiency. ST SegmentHub Team --- URL: https://www.segmenthub.com/pricing/ Volume-based pricing Plans that scale with your traffic. SegmentHub starts at $2,500 per month. What you pay depends on two things: the volume of requests we process for you each month, and the number of platforms you connect. Every plan is month-to-month, with no long-term contract. ## Growth For a single web or mobile platform that needs real-time segmentation from day one. From $2,500 / month Based on your monthly request volume. - Real-time CDP & DMP engine - Anonymous and known profile unification - Real-time segment builder - One connected platform (web or app) - Standard integrations: Google Ads, Meta, GA4, Firebase, Slack - Web, iOS and Android SDKs plus the REST API - Purpose-scoped consent, subject access exports and erasure with a signed receipt - Email campaigns from your own SMTP relay - Mobile and web push from your own Firebase project and VAPID keys - Integration-health alerting to email and a Slack-compatible webhook Get a quote Includes ad server ## Scale For teams running several platforms and activating audiences across their own inventory. Custom Let's talk Priced on request volume and connected platforms. - Everything in Growth - Multiple platforms: web, iOS, Android and offline sources - First-party ad server and media server - Bi-directional CRM sync: Salesforce, HubSpot, Dynamics, Zoho - Server-side tracking - Computed traits and data replay - SMS and WhatsApp through your own Twilio, MessageBird or Vonage account - Daily warehouse export to your own S3 or Google Cloud Storage bucket - Priority support with an agreed response SLA Talk to sales ## Enterprise For organizations with data sovereignty, security review or deployment requirements of their own. Custom Let's talk Includes on-premise and private cloud options. - Everything in Scale - On-premise or private cloud deployment - Raw data access via Hadoop and Spark - Custom data retention periods - Native BigQuery loads and generated Snowflake, Athena and Trino SQL - Declared data region and a per-account privacy report - Dedicated customer success manager - Custom SLA and security review support Contact us ## Prove the value before rollout Enterprise customers can run a free proof of concept tailored to their data, priority use cases and business objectives. Test SegmentHub in your environment before making a rollout decision. ### Your POC report includes - Validated use cases and observed results - Integration and deployment feasibility - Expected business value and rollout recommendations Request a free POC ## What drives your price No per-seat fees and no charges for the segments or campaigns you create. Three factors decide your monthly cost. ### Monthly requests The number of events and API requests we process for you each month — page views, product views, purchases, searches, profile lookups and segment syncs. Higher traffic means more infrastructure, so it is the main lever on price. ### Connected platforms Each platform you connect — your website, iOS app, Android app, CRM or offline sources — adds an identity surface we resolve against. One platform sits at the entry price; multi-platform setups are quoted individually. ### Deployment model Our managed cloud is the standard. On-premise and private cloud installations, custom retention windows and bespoke SLAs are available on the Enterprise plan and priced per engagement. ## Included in every plan Segments and audiences are not metered No per-seat fees for panel users Real-time processing, not batch GDPR and CCPA tooling Documented REST API and SDKs Month-to-month, cancel any time ## Pricing questions ### How much does SegmentHub cost? SegmentHub starts at $2,500 per month. Your exact price depends on the volume of requests we process each month and the number of platforms you connect. Send us your monthly traffic figures and we will quote you directly. ### What counts towards my monthly request volume? The events and API calls we process on your behalf: page views, product views, purchases, searches, profile queries and segment syncs to your advertising and CRM destinations. Creating segments, adding panel users and running campaigns are not metered. ### Are there any commitments or contracts? There are no commitments or contracts. SegmentHub is a month-to-month service and you can cancel your subscription at any time. ### What happens if my traffic grows mid-plan? Because the service is month-to-month, your plan moves with your traffic. We review volumes with you and adjust from the next billing month rather than cutting off collection or throttling your data mid-campaign. ### Do you offer on-premise deployment? Yes. On-premise and private cloud installations are available on the Enterprise plan for organizations with strict data sovereignty requirements, and are priced per engagement. --- URL: https://www.segmenthub.com/privacy-policy/ Privacy Policy Last updated: February 20, 2026 ## 1. Introduction At SegmentHub, we respect your privacy and are committed to protecting the personal data of our users, visitors, and customers. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our website or use our Customer Data Platform (CDP) and Data Management Platform (DMP) services. Please read this policy carefully. If you do not agree with the terms of this privacy policy, please do not access the site or use our services. ## 2. Information We Collect We collect information that identifies, relates to, describes, or could reasonably be linked, directly or indirectly, with a particular consumer or device. The types of information we collect include: - Personal Data: Name, email address, phone number, and company name when you register for an account, subscribe to our newsletter, or contact sales. - Account Data: Billing information, transaction history, and service preferences. - Usage Data: Information about how you use our website and services, including IP addresses, browser types, operating systems, referring URLs, and pages viewed. - Customer Data (Processed on Your Behalf): When you use our CDP/DMP, we process end-user data on your behalf as a "Data Processor" (or "Service Provider"). This data is governed by the agreement between you and SegmentHub, and you remain the Data Controller. ## 3. How We Use Your Information We use the information we collect for various business purposes, including to: - Provide, operate, and maintain our website and platform. - Process your transactions and manage your account. - Improve, personalize, and expand our services. - Understand and analyze how you use our website. - Develop new products, services, features, and functionality. - Communicate with you for customer service, updates, and marketing purposes. - Find and prevent fraud and ensure security. ## 4. Data Sharing and Disclosure We may share the information we have collected about you in certain situations. Your information may be disclosed as follows: - Service Providers: We may share your information with third-party vendors, service providers, contractors, or agents who perform services for us or on our behalf (e.g., payment processing, data analysis, email delivery, hosting services). - Business Transfers: We may share or transfer your information in connection with, or during negotiations of, any merger, sale of company assets, financing, or acquisition. - Legal Obligations: We may disclose your information where we are legally required to do so to comply with applicable law, governmental requests, a judicial proceeding, court order, or legal process. We do not sell your personal information to third parties. ## 5. Data Security We use administrative, technical, and physical security measures to help protect your personal information. While we have taken reasonable steps to secure the personal information you provide to us, please be aware that despite our efforts, no security measures are perfect or impenetrable, and no method of data transmission can be guaranteed against any interception or other type of misuse. ## 6. Your Privacy Rights (GDPR & CCPA) Depending on your location, you may have the following rights regarding your personal information: - Right to Access: You can request copies of your personal data. - Right to Rectification: You can request that we correct any information you believe is inaccurate. - Right to Erasure: You can request that we erase your personal data, under certain conditions. - Right to Restrict Processing: You can request that we restrict the processing of your personal data. - Right to Data Portability: You can request that we transfer the data that we have collected to another organization, or directly to you. To exercise any of these rights, please contact our Data Protection Officer at privacy@segmenthub.com. ## 7. Cookies and Tracking Technologies We may use cookies, web beacons, tracking pixels, and other tracking technologies on the website to help customize the Site and improve your experience. For more information on how we use cookies and how you can manage your preferences, please review our Cookie Settings page. ## 8. Changes to This Privacy Policy We may update this Privacy Policy from time to time to reflect changes to our practices or for other operational, legal, or regulatory reasons. We will notify you of any material changes by posting the new Privacy Policy on this page and updating the "Last updated" date. ## 9. Contact Us If you have questions or comments about this Privacy Policy, please contact us at: Email: privacy@segmenthub.com Address: Nisbetiye mah. Gazi Gucnar sok. No:4/5, 34340 Besiktas/Istanbul, Turkiye --- URL: https://www.segmenthub.com/reporting/ Reporting & measurement # Measure the audience, the action and the delivery. Explore profiles and visitors, break down customer attributes, measure first-party campaign interactions and inspect every activation run from one operational view. ## Audience reports Filter profiles, visitors or both and group results by the attributes that matter. ## Campaign interactions Record decisions, impressions and actions for first-party content campaigns. ## Push delivery Follow targeted, sent, accepted, failed and invalid-token results by day. ## Activation history Inspect audience size, eligible records, additions, removals, rejections and errors. Profiles by loyalty tier 68,920 profiles NewMemberSilverGoldPlatinum Illustrative interface values ## Ask focused questions of customer data Reports reuse the same audience-rule language as segmentation. Filter by attributes, recency and segment membership, then choose the dimensions to summarize. - Search known profiles, anonymous visitors or both. - Render results as bar, doughnut, pie, table or headline text. - Control breakdown dimensions and result limits. - Query a saved report through the API for another workflow. ## Operational answers, not a black box ### What was targeted? Connect campaign results to the audience definition and inspect who qualified before interpreting delivery. ### What reached the destination? Separate eligible, sent, added, removed and rejected records instead of treating every sync as a single number. ### What needs attention? Use statuses, timestamps, duration and recorded errors to find a failing activation or delivery workflow. ## Connect customer insight to activation. Build reports from the same first-party data that powers your audiences and customer experiences.Explore reporting --- URL: https://www.segmenthub.com/security/ Security & privacy Built for privacy by design. SegmentHub processes first-party behavioural data on your behalf. This page sets out how that data is handled, what controls you get, and where your data can live. ## GDPR and CCPA tooling Purpose-scoped consent, subject access exports and right-to-erasure handling are part of the platform rather than something you build around it — and an erasure returns a signed receipt naming every store it reached. See Consent & Privacy. ## Identifiers are hashed before they leave Audiences pushed to advertising networks carry normalized SHA-256 hashes, never raw email addresses. Profiles without an identifier a destination can match are excluded from the upload rather than padded in. ## On-premise and private cloud Where regulation or policy requires data to stay inside your own infrastructure, SegmentHub can be installed there instead of running on our managed cloud. Available on the Enterprise plan. ## Destination credentials stay write-only API tokens and secrets for connected ad networks are entered once and never displayed again in the panel. They can be replaced or deleted at any time, which immediately stops the synchronization that used them. ## What we process, and why Data Purpose Leaves your account as Behavioural events Page, product, search and purchase activity used to build segments Does not leave; used to compute membership Profile identifiers Resolving activity across devices to one person SHA-256 hashes, only to destinations you connect Segment membership Targeting and personalization As audience lists in the ad networks you enable Messaging addresses Delivering email, SMS, WhatsApp and push you have consent for To your own relay, gateway or push service — never ours Consent decisions Recording and enforcing what each person agreed to, per purpose Retrievable on request with their evidence; kept in a durable ledger Exported datasets Loading your own data into your own warehouse Only to the storage bucket you nominate, under your credentials Destination credentials Authenticating audience synchronization and message delivery Never displayed or exported ## Subject rights, end to end The usual gap in a data platform is not refusing a request — it is not being able to say what happened to every copy. SegmentHub owns each of its own stores, so one request reaches all of them and produces an artefact you can hand to a reviewer. ### Consent per purpose Analytics, advertising, personalization, email, SMS and push are decided separately and recorded with their source, timestamp, the wording shown and the notice version. "Never asked" is stored as a distinct state from "declined". ### Enforcement at collection A consent gate can run when an event arrives, not just before a message goes out. Choose per account between recording only, pseudonymising events that lack the purpose, or dropping them outright. IAB TCF v2.2 strings are read directly. ### Access requests One authenticated call returns everything held about a data subject: the visitor record, the linked customer profile, every consent decision with its evidence, and their suppression status. ### Erasure with a signed receipt Queued, audited and fanned out across every profile-store shard, both search indices and the shared caches. The receipt names each store, holds no personal data itself, and is re-verified every time the privacy report is opened. Two things are deliberately kept. An opt-out entry survives erasure in anonymised form, because deleting it would silently re-enable messaging that person the moment they appeared again. The audit trail survives too, because it is the evidence of what the platform did — including the erasure. A per-account data region is recorded alongside the on-premise option above for the residency conversation. Full detail on the Consent & Privacy page. ## Auditability Every audience synchronization is recorded: when it ran, the source audience size, how many records were eligible, how many were added, removed or rejected, how long it took, and the error returned if it failed. If a network stops accepting an audience you can see exactly when that started and what it objected to, rather than discovering it through a campaign that quietly underperforms. You do not have to go looking. An expired destination token, an unusual rejection rate, a relay or gateway that has started refusing sends, and a drop in event volume against the same hour on the same weekday each raise an alert to email and a webhook — one per broken thing, closed automatically with a recovery notice. See Alerts & Health. Our privacy policy covers what we collect on this website and how to reach us about it; the terms of service govern use of the platform, and cookie settings control what this site itself stores. ## Enterprise operations Controls for teams that need accountability, repeatable configuration and limited access—not a shared administrator login. ### Immutable activity history Account mutations are written to a centralized audit record, while the activity report makes changes reviewable by actor, time and affected resource. ### Granular team permissions Separate view and manage rights for audiences, campaigns, reports, media, members, settings, webhooks, API tokens and publishing. ### Scoped API access Create managed API tokens for application workflows instead of distributing member credentials or granting broader panel access. ### Portable configuration Export account configuration, preview an import and apply reviewed changes so setup can be reproduced across controlled environments. ## Reporting a vulnerability If you believe you have found a security issue in SegmentHub, email security@segmenthub.com with a description and the steps to reproduce it. Please give us reasonable time to fix it before disclosing it publicly, and do not access, change or delete data that is not yours while testing. Our contact details are also published in security.txt. ## Going through a security review? Procurement and information-security teams usually need specifics: data residency, retention periods, sub-processors, encryption, access control, incident response and a data processing agreement. We answer those directly, against your questionnaire, rather than in marketing copy — and the Enterprise plan includes support through the review itself. Request security documentation Or email privacy@segmenthub.com directly. --- URL: https://www.segmenthub.com/sms-whatsapp/ SMS & WhatsApp # The channel people read, without the surprises. Send SMS and WhatsApp campaigns through your own Twilio, MessageBird or Vonage account, to the same real-time audiences that drive email, push and on-site personalization. What a message costs is on the page before you send it, and one STOP silences every campaign that reaches that number. Book a DemoRead the SMS cost guide SHOP Your cart is still saved. 3 items, 1,240 TL — finish your order: sgh.to/k7Xq4m Reply STOP to unsubscribe 147 characters · 1 billable segment Quiet hours respected Consent verified ## One-time Send now or at a chosen moment to every consenting, reachable number in one or more audiences. A delivered campaign is locked, because on this channel a second send is a second invoice — cloning is how you run it again. ## Recurring Run daily, weekly or monthly in the account timezone. The audience is resolved again on every run, and a weekly campaign reuses its short links so clicks accumulate on one row instead of scattering. ## Triggered Respond to a customer state such as an abandoned cart after the configured delay, minimum value and eligibility checks — reading the same cart signals email and push already use. ## The cost is on the page before you send Every message is billed at your own gateway, immediately. One pasted character can triple that bill, and nothing in the gateway response explains why — so the count is shown as the marketer types. Typed as plain text Your cart is still saved. Finish your order today. 147 characters · 1 billable segment · 13 left · GSM-7 One curly quote pasted in Your cart’s still saved. Finish your order today. 148 characters · 3 billable segments · 53 left · Unicode ### Counted the way you are billed The estimate handles the extended characters that cost two septets each, the drop from 160 to 153 once a message goes multi-part, and the equivalent drop in Unicode. Where the gateway reports its own count, that number wins — it is the one on the invoice. ### Short links, not tracked URLs An email-style tracking URL runs past 120 characters and would add a whole billable segment to every message. Links are shortened to about twenty-five, with your UTM parameters applied to the destination so your own analytics still sees the campaign. ### Budgets and throttles Per-second, per-minute and per-day limits match what your gateway actually accepts, and a daily budget spreads a large audience across several runs rather than spending it all at 09:00. ## STOP works everywhere, once Somebody who replies STOP means stop messaging me on this number — not stop using this particular protocol. SMS and WhatsApp share one consent decision, one suppression entry and one frequency budget. ### One suppression list The durable list that holds email opt-outs now holds phone numbers too, checked when the audience is resolved and again for each message on the way out — because a campaign fanned out at 09:00 must not message somebody who replied STOP at 09:05. ### Keywords read carefully STOP, START and HELP are honoured when the whole reply is one of them, with accents and punctuation folded. Somebody writing a sentence about Sundays is making a request to a human, and unsubscribing them silently would be worse than not reading it at all. ### An import cannot undo an opt-out Re-uploading last year's list is the classic way to resurrect people who opted out. Here it does not work: only a deliberate act — a panel action or a completed double opt-in — can lift an existing opt-out. ### Quiet hours are on by default 21:00–08:00 out of the box, because US rules bar marketing messages outside 08:00–21:00 local and several EU markets set their own windows. A campaign that comes due inside the window is postponed to its end rather than sent. ### Numbers stored in one shape Everything compares numbers by exact match, so nothing is stored until it is normalized to E.164 against your default country. A number kept in the wrong shape reads as reachable, never matches its own opt-out, and cannot be found when that person replies STOP. ## Your gateway, your numbers, your rates Bring your own gateway: connect Twilio, MessageBird or Vonage. The account, the sender registration, the country routing and the rate card stay yours — SegmentHub never resells telecom. Validated before it is saved: credentials are encrypted at rest and the connection is tested on save. A misconfiguration aborts the whole job rather than spending your rate limit on ninety-nine identical rejections. WhatsApp with template enforcement: a marketing send is always business-initiated, so the builder requires an approved template name and language instead of letting free text be rejected weeks later by an error code nobody can act on. Replies and receipts come back: one inbound webhook carries both delivery receipts and keyword replies, guarded by a per-integration secret and, where the gateway signs its requests, a verified signature. Campaign funnel Targeted18,430 Sent18,102 Delivered17,689 Clicked2,244 Opted out96 Billable segments are reported beside the send count, and an opt-out is attributed to the campaign that prompted it. Clicks are counted per link rather than per person. Illustrative interface values. ## Add the handset to the journey. The same audiences, the same cart signals and the same consent record already driving your email and push campaigns — now on SMS and WhatsApp.Plan your first campaign --- URL: https://www.segmenthub.com/terms-of-service/ Terms of Service Last updated: February 20, 2026 ## 1. Acceptance of Terms By accessing and using the SegmentHub website, products, and services (collectively, the "Services"), you agree to comply with and be bound by these Terms of Use ("Terms"). If you do not agree to these Terms, you may not access or use the Services. ## 2. Description of Service SegmentHub provides a Customer Data Platform (CDP) and Data Management Platform (DMP) that allows businesses to aggregate, analyze, and act upon customer data. The specific features and limitations of your access will depend on your subscription plan. ## 3. User Registration and Security To use certain features of the Services, you must register for an account. You agree to: - Provide accurate, current, and complete information during the registration process. - Maintain and promptly update your account information. - Maintain the security and confidentiality of your login credentials. - Accept responsibility for all activities that occur under your account. ## 4. Data Privacy and Compliance As a user of SegmentHub, you are solely responsible for ensuring that your use of the Services complies with all applicable data protection and privacy laws (such as GDPR, CCPA, etc.). You represent and warrant that you have obtained all necessary consents and rights to collect, process, and store the customer data you input into SegmentHub. For more details on how SegmentHub itself handles data, please review our Privacy Policy. ## 5. Acceptable Use Policy You agree not to use the Services to: - Upload, post, or transmit any data that is unlawful, harmful, threatening, abusive, or otherwise objectionable. - Infringe upon the intellectual property rights or privacy rights of any third party. - Attempt to gain unauthorized access to any portion of the Services or any connected systems or networks. - Transmit any viruses, worms, defects, Trojan horses, or any items of a destructive nature. - Use the Services for any illegal or unauthorized purpose. ## 6. Intellectual Property Rights All content, features, and functionality available through the Services—including but not limited to design, text, graphics, software, and the SegmentHub logo—are the exclusive property of SegmentHub and are protected by international copyright, trademark, patent, trade secret, and other intellectual property laws. You retain all rights to the data you upload or process using SegmentHub. We do not claim ownership over your proprietary customer data. ## 7. Limitation of Liability In no event shall SegmentHub, its directors, employees, partners, agents, suppliers, or affiliates, be liable for any indirect, incidental, special, consequential or punitive damages, including without limitation, loss of profits, data, use, goodwill, or other intangible losses, resulting from: - Your access to or use of or inability to access or use the Services. - Any conduct or content of any third party on the Services. - Any content obtained from the Services. - Unauthorized access, use or alteration of your transmissions or content. ## 8. Termination We may terminate or suspend your account and bar access to the Services immediately, without prior notice or liability, under our sole discretion, for any reason whatsoever and without limitation, including but not limited to a breach of these Terms. Upon termination, your right to use the Services will immediately cease. If you wish to terminate your account, you may simply discontinue using the Services or contact support for formal account closure. ## 9. Changes to Terms We reserve the right, at our sole discretion, to modify or replace these Terms at any time. If a revision is material, we will provide at least 30 days' notice prior to any new terms taking effect. What constitutes a material change will be determined at our sole discretion. ## 10. Contact Us If you have any questions about these Terms, please contact us at: Email: legal@segmenthub.com Address: Nisbetiye mah. Gazi Gucnar sok. No:4/5, 34340 Besiktas/Istanbul, Turkiye --- URL: https://www.segmenthub.com/web-push/ Web push # A push channel that needs no app. Most of your audience will never install an app. Web push reaches them in the browser they already use — on your own VAPID keys, targeted by the same real-time audiences, and governed by the same quiet hours, frequency caps and consent rules as every other channel. Book a DemoSee the full push module Back in stock The size you were looking at is available again. shop.example.com No app required One budget per person ## Every major browser Chrome, Edge, Firefox, Opera, Samsung Internet and Safari on both desktop and mobile, over the standard Web Push Protocol. No SDK to ship and no store review to wait for. ## Your own VAPID keys Generate a key pair in the panel or paste the one you already have, so subscribers acquired on another tool come with you. The private half is encrypted at rest and never leaves the platform. ## Targeted per platform A campaign can name the platforms it is written for, so a message worded for a phone never lands in a desktop browser. The filter is applied before the newest-device pick, so a web-only campaign finds a person's newest browser rather than skipping them. ## Live in an afternoon Three steps, and the last one is the only code you write. 1 ### Generate a key pair One click in push settings, or paste an existing pair. A pasted pair is proven to actually be a pair before it is saved — a mismatched one passes every structural check and then fails weeks later as an unexplained rejection. 2 ### Copy the service worker The integrations tab hands you a service worker and a subscription snippet with your account, API host and public key already filled in. Host the worker at your site root and the snippet does the rest. 3 ### Ask at the right moment Call the subscription snippet when a visitor has shown intent, not on first paint. Every subscriber lands on the existing customer profile, so audiences, reports and reach estimates include them immediately. Rotating keys is destructive, and is treated that way. A browser binds its subscription to the key it subscribed with, so replacing a pair stops delivery to every current subscriber until they subscribe again. The panel requires an explicit confirmation and warns before it happens, rather than letting a routine-looking save empty your list. ## One module, two transports Web push is not a second product with its own rules. It rides the push module you already know, so everything that governed mobile notifications governs these too. ### Shared delivery policy - • Quiet hours in the account timezone - • Frequency caps counted per person, so a phone and a browser share one budget - • The same consent purpose — holding a subscription is not consent to be notified - • Message TTL and collapse-key controls - • Subscriptions expire on the same retention rules as every other device ### The same campaign shapes and reports - • One-time, recurring and triggered sends, including cart reminders - • Title, body, image, deep link and a custom data payload - • Delivered and opened reported back through your existing tracking - • Unsubscribed browsers pruned automatically on the next send - • Reach estimated by the same query the scheduler resolves, so the two cannot drift ## Built for a value only a visitor chooses A push subscription address is picked by an anonymous browser and then called by our servers — which makes it the one value in the whole module that an untrusted party controls. HTTPS only, because the authorization token that accompanies a push is a bearer credential. A default allowlist of the real browser push services, so an arbitrary address a visitor names is never called. It is overridable per environment for self-hosted deployments testing against a local service. Both checks run twice — when a subscription is registered, and again when a message is sent. Storage is not a trust boundary, and a name that resolved publicly at registration can resolve differently later. Payloads are encrypted end to end under the standard content encoding, so the push service carries the message without being able to read it. Push audience by platform Web — desktop41,208 Web — mobile28,940 Android app12,417 iOS app9,860 One person reachable on several platforms still receives one message, on their most recently used device that matches the campaign. Illustrative interface values. ## Reach the visitors who never installed anything. Web push shares its audiences, its delivery policy and its reports with mobile push, email and SMS, so one story reaches each customer once.Plan your first campaign --- URL: https://www.segmenthub.com/webhooks/ Webhooks & extensibility # When there is an endpoint, there is a path forward. Send customer events or audience-driven payloads to systems beyond native destinations with configurable methods, headers, authentication, batching and delivery timing. Discuss an integrationView API Reference ## Deliver the data the receiving system expects A webhook can react to selected events, synchronize selected audiences or run on a configured schedule. Shape the request without waiting for a dedicated connector. Methods GET, POST, PUT, DELETE Delivery Sync or asynchronous Control Timeout, proxy, delay Scale Batch-size configuration POST /customer-journey Authorization: Basic [credential] Content-Type: application/json { "profile": "{{profileId}}", "audience": "high-intent", "event": "product_viewed", "occurredAt": "{{timestamp}}" } ## Event-driven Select the account events that should notify an order system, automation tool or internal service. ## Audience-driven Synchronize selected audiences so another system can act on the same customer eligibility. ## Scheduled Set execution timing and delay when the receiving workflow should not run immediately. ## Native where it helps. Extensible everywhere else. Choose the integration path that matches the destination. PathBest forOwnership Native destinationSupported advertising and platform workflowsSegmentHub manages provider behavior WebhookHTTP-capable tools and internal servicesYou define endpoint and payload REST APIBidirectional application integrationYour application controls the workflow ## Connect the system already in your stack. Use native destinations where available and configurable webhooks or APIs everywhere else.Plan the connection --- URL: https://www.segmenthub.com/posts/on-site-popups-without-code/ - Home Blog On-site Popups, Bars and Banners Without Writing Code Update • Oct 18, 2026 • 6 min read # On-site Popups, Bars and Banners Without Writing Code Until now, every popup, bar and banner on a customer's site was JavaScript written for that site. The Gallery replaces that code with designs a marketer builds in the panel and the tag already on the page draws. SH SegmentHub Team Product & Engineering LinkedIn WhatsApp Email Free shipping on orders over $50 · ends in 02:14:09 Just for you 20% off knitwear you@example.com Get my code Ask a marketing team what they want on their own website and the list is always similar: a welcome popup with a discount, a bar announcing free shipping, a countdown before a sale ends, a signup form that doesn't feel like a wall, a banner inside a category page. None of it is unusual. Yet on most sites each of those creatives is a small software project: someone writes the markup, styles it against the theme, decides when it opens, wires up its tracking and fixes it on mobile. That was true of SegmentHub as well. Campaigns have long been targeted by real-time segments, scheduled, prioritised and frequency-capped in the panel — but the part that drew the creative on the page was JavaScript written for each customer's site. A new placement, or a new customer, meant new code. The Gallery removes that step. ## Pick a template, adjust it, attach it The Gallery is a catalogue of 26 ready-made templates in five kinds: - Popups — a centred window over a dimmed page; - Fullscreen — a takeover of the whole viewport; - Slide-ins — a card from a corner, or a drawer from the edge of the page, that leaves the page usable; - Announcement bars — at the top or bottom of the window, over the page or pushing it down, or inside your header; - Inline banners — inside the page, in a placement you define with a CSS selector. Opening a template gives you an editor with a live preview: texts, images from your media library, colours, sizes, position, animation, buttons and what they do, and how the design can be closed. A brand kit applies your colours, corner radius and font choice the moment a template opens, so a new design starts on-brand rather than in the template's defaults. A design you want to reuse can be saved as one of your account's own templates. Popups and slide-ins can carry a teaser: a small tab on the edge of the page that stands in for the design until the visitor opens it, and can come back after it is closed. The finished design is then chosen in a campaign, exactly where image and HTML variations were chosen before. Everything a campaign already had still applies: the platforms, the events it answers, the attribute and segment rules, the start and end dates, the priority, the frequency cap and the variations. ## One design, three screen sizes A design has a base layout and its own adjustments for tablet and mobile: a narrower width, a popup that becomes a sheet at the bottom of a phone screen, an image hidden on small screens. A design can also be switched off for one device class entirely, and the campaign's next matching variation then takes the place. The preview switches between the three, so what you approve is what each visitor gets. ## Shown when it is useful Popups, slide-ins and bars open on a display trigger chosen on the campaign: - immediately, or after a delay that counts only while the tab is visible; - at a scroll depth; - on exit intent — the pointer leaving through the top of the window; touch screens have no pointer, so there a quick upward scroll or a fallback delay stands in; - after a period of inactivity. Two details matter more than they look. The frequency cap is now counted when a design is actually seen, not when the campaign is selected for the page — a popup waiting for exit intent that never appears no longer uses up its cap. And a campaign can stay quiet for a number of days after a visitor has closed it, clicked it or submitted its form, so nobody is asked twice for an address they just gave you. Each placement shows one campaign at a time, by priority, so two popups never open together, while a bar and a popup in different placements can. ## Forms, coupons and countdowns A design is built from blocks, and some of those blocks do real work: - Countdowns to a fixed moment, to the campaign's end date, or a number of minutes from this visitor's first view. When one runs out it can hide itself, hide the design or show a message. - Coupons with a copy button. A code can be typed into the design, or each visitor can receive a code of their own from a pool you upload. - Signup forms for email, phone and name. Each field is written to the visitor's own profile, and a ticked consent box is recorded together with the wording the visitor agreed to. An address alone is not permission to send, and someone who opted out earlier stays opted out. Form fields are never copied into events or analytics. - Personal greetings from the visitor's profile, with a fallback for people you don't know yet — "Welcome back, Ada" or "Welcome back, there". - Product recommendations picked for the visitor by the recommendation engine, inside the popup, slide-in or banner. ## Spin-to-win and scratch cards Popups, fullscreen designs and slide-ins can also hold a game: a wheel or a scratch card, often behind an email field. For a game to be fair, the browser must not decide the outcome. The visitor's browser is sent only what it has to draw — the names and colours on the wheel, never the odds or the codes. The prize is drawn on SegmentHub's side, once per visitor; asking again returns the same result. A prize can hand out a unique code from a coupon pool, and a pool's daily limit bounds what any one day can give away. ## Measured where you already look Every design reports its outcomes the same way, wherever it runs: views (at least half of it visible for a second), opens from a teaser, clicks (with the button that was clicked), closes (with how it was closed), form submissions and plays. They count in the campaign report, and each design has its own report by day, by device class and by the campaigns that use it. The same outcomes become SegmentHub events, so they work like any other behaviour: "everyone who closed the autumn popup" can be a segment, and an event action can tag the people who clicked. Each outcome can be switched off if you don't want it stored. They also go to Google Analytics 4 through whatever the site already has — gtag() or the GTM dataLayer — using GA4's own promotion vocabulary: view_promotion, select_promotion, close_promotion and generate_lead. The names can be changed per account, GA4 can be switched off, and the visitor's profile ID is never sent. ## Nothing new to install There is no new snippet. The SegmentHub tag already on your site recognises a Gallery campaign and loads the on-site code only on pages that have one, so pages without a design pay nothing extra. Before a campaign goes live, a preview link shows a design on your real site. Designs are drawn inside their own isolated layer (Shadow DOM), so your theme's CSS can't break them and theirs can't leak into your page. Texts are inserted as text, never as code, and images come from your own media library. Dialogs trap and return keyboard focus, close with Escape when the design allows it, and animations stop for visitors who ask their device for reduced motion. And campaigns that are evaluated on a visitor's data respect the personalization consent the visitor gave — see Consent & Privacy. ## Where this sits in SegmentHub The Gallery is part of the Media Server, which delivers every on-site campaign — inline placements as well as overlays — to the segments SegmentHub keeps up to date in real time. The full list of kinds, triggers and blocks is on the On-site Marketing page. Explore On-site Marketing --- URL: https://www.segmenthub.com/posts/sms-cost-and-compliance/ - Home Blog What an SMS Campaign Actually Costs Tech • Sep 6, 2026 • 6 min read # What an SMS Campaign Actually Costs Email fails softly: a wrong audience wastes a send. SMS fails expensively, immediately, and on your own invoice. Three decisions made before the first campaign determine whether the channel is cheap or ruinous. SH SegmentHub Team Customer Journey Guides 148 characters 3 billable segments · Unicode One character changed everything Every marketing channel has a failure mode that only shows up at scale. For email it is a damaged sending domain. For push it is uninstalls. For SMS it is an invoice that is three times what anybody estimated, from a gateway that will not explain why — and a regulator's letter about people who asked to be left alone. Both problems are avoidable, and both are avoided in the same place: before the send, not in the report afterwards. ## 1. A message is not billed by the character It is billed by the segment. A message written entirely in the basic GSM alphabet fits 160 characters into one segment. A message containing a single character outside that alphabet switches the whole message to a 16-bit encoding, and the limit drops to 70. The characters that trip this are not exotic. They are the ones a word processor inserts silently: the curly apostrophe, the em dash, the ellipsis, the non-breaking space, and most accented letters outside a handful of Western European ones. Paste a sentence from a document into a campaign body and the encoding can flip without a single visible change on screen. A 148-character message is one segment in the basic alphabet and three once it becomes Unicode. On a million-recipient list, that is two million messages nobody budgeted for. There are two more details that a naive character count gets wrong: - Some basic-alphabet characters cost double. The euro sign, curly braces, square brackets, the tilde, the pipe, the backslash and the caret each consume two units of the 160. - Multi-part messages get smaller, not just more numerous. Once a message needs more than one segment, each segment gives up space to the header that reassembles them — 160 becomes 153, and 70 becomes 67. A message at 161 characters is not "one and a bit"; it is two segments of 153. The practical rule: compute the segment count on the server, with the same code that will count it at send time, and show it live in the campaign builder. A count reimplemented in the browser will eventually disagree with the one that bills you, and it will disagree in the direction nobody notices. Count the opt-out sentence too. "Reply STOP to unsubscribe" is twenty-five characters that arrive on the invoice like any other. ## 2. Links are the other place the money goes Email tracks clicks by rewriting every link into a long signed URL that identifies the campaign and the recipient. Copy that pattern into SMS and you have added 120 characters to every message — often a whole extra segment, on every send, forever. The answer is a short link: about twenty-five characters, minted once per campaign rather than once per recipient. That costs one thing worth being honest about — clicks are then counted per link rather than per person, because per-person attribution requires a distinct URL per recipient, which is exactly the per-message row this approach exists to avoid. Two details make short links behave well: - Apply your UTM parameters to the destination before it is shortened. The recipient follows an opaque link, but your analytics still sees the campaign that sent them. - Make the token random, and drop the ambiguous characters. A sequential token lets anyone enumerate every campaign's destinations by counting. And these links get read off a phone screen and typed by hand, so zero against capital O, and one against lowercase L, are worth removing from the alphabet. ## 3. STOP is a legal instruction, and it arrives with nothing attached An inbound SMS carries a phone number. No cookie, no session, no visitor id. That single fact shapes everything about consent on this channel. The suppression list is the most load-bearing thing in the system. It has to outlive the behavioural profile — someone who opts out and then stops visiting for six months must not become messageable again when their profile expires. It has to be checked when the audience is resolved and again for each message on the way out, because a campaign fanned out at 09:00 must not message somebody who replied STOP at 09:05. And when the list cannot be read, the correct behaviour is to refuse to send: an empty list must never be interpreted as "nobody has opted out". One number, one decision. If you send both SMS and WhatsApp, they reach the same person at the same number. Keeping separate opt-out lists per protocol means an opt-out on one leaves the other free to keep messaging — which is precisely the failure the list exists to prevent. Read the keyword, not the sentiment. Honour STOP, START and HELP when the entire reply is one of those words, with accents and punctuation folded so that a message typed on a localised keyboard still matches. Somebody who writes "please stop sending these on Sundays" is making a request to a human being. Unsubscribing them silently is worse than not reading the message at all. Honour the carrier's opt-out too. A person can opt out at the network without your platform ever seeing a message. The gateway then rejects your next send with a specific code. Treat that as an opt-out and record it as one — not as a bad number, which is what it looks like if you only read the HTTP status. Make re-subscription hard. Re-uploading last year's list is the classic way to resurrect people who opted out. An opt-out should never be lifted by a bulk import or an inferred signal; only a deliberate act — a confirmed double opt-in, or a human action recorded in the panel — should be able to. ## Quiet hours are not a nicety US rules bar marketing messages outside 08:00–21:00 local time, and several EU markets set their own windows. Unlike email, where a badly timed send is merely ignored, a 02:00 SMS is a complaint and sometimes a fine. Default the window to on, and postpone a campaign that comes due inside it rather than dropping it. And check the implementation against the case that a naive comparison gets exactly backwards: a window from 21:00 to 08:00 wraps midnight, so "is now inside the window" is not start < now < end. ## Store the number in one shape, from the first write Every comparison in an SMS system is an exact match: the suppression lookup, the send-time deduplication, the inbound STOP lookup. That means 0532 123 45 67, +90 532 123 45 67 and 905321234567 are three different people to all of them. Normalise to E.164 before anything is stored, using an explicit default country rather than a guess, and refuse a number that will not parse rather than writing it and finding out later. A number stored in the wrong shape produces a profile that reads as reachable in the panel, never matches its own opt-out, and cannot be found when that person replies STOP. It is the failure mode that looks like it worked. ## The checklist before your first send - Confirm the segment count shown in the builder is computed by the same code that counts at send time. - Preview the exact text a handset receives, opt-out sentence included. - Import your existing do-not-message list on day one. - Set the daily budget and the per-second rate to what your gateway actually accepts. - Point the gateway's inbound webhook at the platform, and verify a test STOP suppresses the number. - Set the quiet-hours window for the markets you send to, not just your own timezone. - Decide the default country used to normalise numbers, and check what happens to one that will not parse. See how targeting, cost estimation, consent and reporting fit together on the SMS & WhatsApp page, or compare the same controls in the Email Campaigns module. Explore SMS & WhatsApp --- URL: https://www.segmenthub.com/posts/proving-data-erasure/ - Home Blog Deleting Is Easy. Proving It Is the Hard Part Strategy • Sep 3, 2026 • 5 min read # Deleting Is Easy. Proving It Is the Hard Part Almost every vendor will honour a right-to-erasure request. Very few can tell you what happened to the copy in the profile store, the search index and the caches — which is the only part a regulator, or an enterprise security reviewer, actually asks about. SH SegmentHub Team Customer Journey Guides Deletion receipt Every store named, signature verified. The artefact, not the 200 OK Ask a marketing team how they handle a deletion request and you will usually get a confident answer: the customer is removed from the email tool. Ask where else that person exists and the confidence goes. In a typical stack the answer is: the email tool, the CDP, the analytics warehouse, a reverse-ETL cache, three ad platforms' custom audiences, and whatever a data scientist exported to a notebook last quarter. That gap — between "deleted from the tool" and "deleted" — is the single most common complaint about privacy tooling in the category, and it is not because vendors refuse. It is because no one vendor owns enough of the stack to answer the question. ## A subject is a person, not a row The first place an erasure goes wrong is scope. A customer data platform holds at least two records for most people: an anonymous visitor record created before they identified themselves, and a customer profile created when they did. They are linked, and they are separately identifiable. Erase only the profile and the visitor record survives, still carrying the behaviour that was used to build the profile, still linkable to a new identification tomorrow. Erase only the visitor and the profile remains with the email address on it. So a request against either half has to reach both — and a profile with an unusually large number of linked visitor records should be refused outright rather than half-erased, because a partial erasure is worse than a rejected one. ## Where the copies actually are A real-time CDP is a fan-out architecture: the same person exists in several stores because each one answers a different question quickly. An honest erasure names all of them. - The operational profile store, which is usually sharded — so the erasure runs on the node that owns each identifier, not once against a single database. - The search indices that answer audience queries, deleted by query and then refreshed immediately, so the panel stops returning the subject in the same minute rather than at the next indexing cycle. - Side state: saved cart contents, "seen since the last cycle" sets, device and subscription registries. These are the ones that get forgotten, and they are exactly the ones that would resurrect somebody. - The consent ledger rows recording that person's decisions. Everything above is inside the platform, which is what makes a single-pass erasure possible at all. Anything outside it — your warehouse, your bucket, an ad platform's audience — needs its own answer, and a privacy report that pretends otherwise is worse than one that says so plainly. ## Three things a good erasure keeps on purpose "Delete everything" sounds right and is wrong in three specific ways. The suppression entry stays, hashed. If somebody unsubscribed and then asked to be erased, deleting their opt-out record silently re-enables messaging them the moment they appear again. That is the opposite of what they asked for. Keep the row, anonymise the address it holds, and the list still recognises them without storing them. The audit trail stays. It is append-only, and it is the evidence of what the platform did — including this erasure. A system that deletes its own record of deleting cannot demonstrate compliance with the request it just fulfilled. Your own archive is yours. If raw events are written to a bucket you own under a retention policy you set, the platform should say so rather than implying it reached in there. Ownership is the honest answer, and it is a better one than a vague claim. ## The receipt is the deliverable An API returning 200 proves that a request was accepted. It proves nothing about what happened afterwards, and asynchronous work is exactly where a partial failure hides. So the artefact that matters is a signed receipt: which stores were touched, how many records each one reported, when the work finished, and a signature over all of it. Sign it with a secret the platform holds, and re-verify it every time the report is displayed rather than trusting a stored "verified" flag. A green tick that was never actually checked is worse than no tick at all, because it is believed. One detail worth insisting on: the receipt must contain no personal data. A receipt carrying the erased email address defeats the erasure it certifies. An identifier and a hash are enough to tie it to the request. ## Make failure loud A partial erasure that quietly retries forever is the worst available outcome: it looks fine on a dashboard, and it produces no artefact anyone can act on. Mark it failed, record the reason, and surface it. Somebody being told "this erasure did not finish, here is why" can escalate. Nobody can escalate a silent retry loop. The same instinct applies at the other end. Before each record is removed, write every consent purpose on it to denied. That looks pointless on a record about to disappear, and it is not: if the same person is seen again tomorrow, they start from no permission rather than from whatever a stale integration last asserted. ## Consent is the half that prevents the request Erasure is the remedy. Consent is the control, and it works best when it decides what is collected, not only what is sent. Three properties make it defensible: - Purposes are separate. Analytics, advertising, personalization, email, SMS and push are different lawful bases. One checkbox standing in for all six is not consent, it is a formality. - "Never asked" is not "said no". Collapsing the two loses the ability to distinguish a person who declined from one who was never given the choice — and those need different treatment. - Resolution is biased towards not processing. A newer decision wins; a withdrawal is never lifted by a grant arriving from a bulk import or an inference. Only a deliberate act can re-grant. And the enforcement itself should be gradual. An enforcement setting that is off by default, with a pseudonymise mode between "off" and "drop", lets a team turn on the gate for one purpose and watch what happens — rather than discovering on a Monday that a strict setting silently stopped a third of their ingestion. ## What to ask a vendor - Name every store a deletion request reaches. Not "our systems" — the list. - What is kept deliberately, and why? - What artefact do I receive, and can it be verified after the fact? - What happens when an erasure fails halfway? - Can consent stop collection, or only stop sending? - Are consent decisions per purpose, and is the evidence — source, timestamp, wording, notice version — retrievable? See how consent, subject access and erasure are implemented on the Consent & Privacy page, or read the platform-level controls on the security page. Explore Consent & Privacy --- URL: https://www.segmenthub.com/posts/email-consent-and-deliverability/ - Home Blog Email Consent, Suppression and Deliverability Tech • Sep 2, 2026 • 3 min read # Email Consent, Suppression and Deliverability Segmented email fails in a different way than push does. A wrong audience wastes a send; a wrong consent record damages a sending domain that took years to build. Here is where each decision belongs. SH SegmentHub Team Customer Journey Guides Consent verified Checked at targeting, and again at send. Suppression list applied A customer data platform is built to forget. Behavioral events age out, anonymous visitors expire, and profiles that go quiet are eventually removed — which is exactly right for data collected to describe someone's current intent. An unsubscribe is the one record that must survive all of it. ## An opt-out is not behavioral data If consent is stored only alongside the behavioral profile, then a customer who unsubscribes and then stops visiting for a few months has their opt-out quietly garbage-collected with the rest of their record. The next time they identify themselves, they are mailable again. That is not a stale segment; it is a compliance incident. So consent is kept in two places on purpose. The subscription state lives on the customer profile, where the audience builder can target it like any other attribute and a reach estimate can count only mailable people. The opt-out itself is also written to a permanent suppression list that retention rules never touch, and that list is the final gate before every message. ## Check it twice, because time passes Between the moment a campaign resolves its audience and the moment the last message leaves the queue, minutes or hours go by. A large send fanned out at 09:00 must not mail someone who unsubscribed at 09:05. The practical rule is that filtering happens at both ends: the audience query excludes non-consenting profiles when the recipient list is built, and the suppression list is checked again for each individual message on the way out. If the suppression data is unavailable, the correct behavior is to fail the job rather than send — an empty list must never be read as "nobody has opted out". ## Make the safe direction the default Consent arrives from several places: a signup form, a preference centre, an API call, a bulk import, a bounce notification. When two sources disagree, the resolution should be biased towards not sending. An unsubscribe, a hard bounce or a spam complaint should never be overwritten by a subscribe arriving from an import or an integration; only an explicit, deliberate re-subscribe should lift it. Every other part of the pipeline is allowed to be wrong in the direction of mailing fewer people. ## Deliverability belongs to your domain Mail sent through your own SMTP relay carries your reputation, not a shared pool's. That is an advantage worth protecting, and it means the platform's job is to be a careful tenant of your server: - Validate the connection before the settings are saved, and store credentials encrypted. - Enforce per-minute, per-hour and per-day rate limits, plus a cap on concurrent connections and messages per connection, since most relays limit harder than customers expect. - Keep the unsubscribe link on the sending domain where possible — it reads as legitimate to both the recipient and the receiving mail server. - Publish SPF, DKIM and DMARC records and monitor the return path before the first campaign, not after the first block. ## Do not call it delivered An SMTP relay answering with a success code means the next hop accepted the message. It does not mean the message reached an inbox; asynchronous bounces arrive later, and spam placement never announces itself at all. Reporting should say sent and mean "accepted by your relay", then show bounced, unsubscribed, complained and failed alongside opens and clicks. A dashboard that reports a confident delivery number is the kind of metric that stays green while a sending domain is being blocked. ## Consent checklist before the first campaign - Import the existing do-not-mail list from your previous provider on day one. - Confirm the audience reach estimate applies the consent filter, so the number is mailable people. - Set rate limits to match what your relay actually accepts. - Decide whether the preference page is hosted by you or by the platform. - Verify SPF, DKIM, DMARC and the return path. - Send a test through the real pipeline, not a preview-only render. See how audiences, scheduling, templates and reporting fit together on the Email Campaigns page, or compare the same controls in the Mobile Push module. Explore Email Campaigns --- URL: https://www.segmenthub.com/posts/warehouse-export-partitions/ - Home Blog Exporting to the Warehouse Without Duplicating Rows Tech • Aug 31, 2026 • 6 min read # Exporting to the Warehouse Without Duplicating Rows "Can we get our data out?" is the question that decides enterprise deals, and the honest answer is rarely about volume. It is about whether a failed night, a backfill and a re-run can all happen without corrupting somebody's revenue model. SH SegmentHub Team Customer Journey Guides events/ dt=2026-09-05/ part-00001.parquet _load.sql _manifest.json manifest present = safe to load Most export features are built as a nightly job: at 02:00, write yesterday. It is the obvious shape, it demos well, and it is wrong in four ways that only appear in production. - A partition that fails gets its next attempt in 24 hours. - A re-export somebody asks for at 10am waits until tomorrow. - Every tenant's export lands in the same hour, so the load is at its peak exactly when nobody is watching. - A backfill is a separate code path — which means it is the path with the bugs, because it runs a hundred times less often than the one that works. There is a better organising idea, and everything else follows from it. ## A partition is a unit of work that can be redone Model the export as a ledger of (dataset, day) pairs rather than as a schedule. Each pair has a state: never attempted, queued, running, completed, or failed with a next-attempt time. A sweep runs frequently — every fifteen minutes, say — asks which pairs are due, and does a bounded number of them. The scheduled export, a ninety-day backfill, a retry after a bucket outage and a re-export queued by hand in the UI are then the same code path reaching the same row. That is what makes it impossible for any of them to double a row in the warehouse, and it is worth preserving through every future change to the feature. Three rules keep the ledger honest: - Claim the row before writing a byte. An overrunning sweep must not start a partition a previous sweep is still working on. A claim older than a few hours is assumed dead and reclaimed — that is the case where a worker was killed mid-upload. - Cap the work per account per sweep. One tenant catching up on three months must not hold the pipeline while everyone else waits. Order queued work first, then oldest day, so a backfill fills forward rather than leaving a hole in the middle. - Never export today. Today's partition is not closed. Writing it produces a file that has to be replaced tomorrow, and in the meantime somebody's dashboard shows a partial day as if it were a real one. ## The commit marker is the whole reliability story Object storage has no transactions. A run that dies halfway leaves real files in a real folder, and a loader reading that folder cannot tell them from a complete set. The fix is a marker file written last. Write the data parts, delete any stale parts a longer earlier run left behind, and only then write a manifest. A reader now has one cheap test: if the manifest exists, the partition is complete and safe to load. If it does not, the next sweep will overwrite what is there. Make the manifest carry its weight while you are at it — the schema, per-file row counts, byte counts and checksums, and a line saying where the rows came from. That last field answers the first question anyone ever asks about an export: "why does this day have fewer rows than I expected?" The stale-part deletion matters more than it looks. A re-run that produces three parts where the previous run produced five leaves two orphans behind, and a wildcard load will happily read all seven. "Replace the partition" has to be literally true, not approximately true. ## Layout details that decide whether anyone can load it Two file-naming conventions are worth treating as non-negotiable. Use Hive-style partition directories. A folder named dt=2026-09-05 is recognised as a partition column, with no configuration, by BigQuery, Athena, Redshift Spectrum, Spark and DuckDB. A folder named 2026-09-05 means the analyst declares every partition by hand. Prefix data files and metadata files differently. Data as part-*, metadata with a leading underscore. Loaders read .../dt=.../part-*, so a manifest and a SQL script sitting in the same folder can never be parsed as data. Under a plain * glob, they will be — and the resulting error message will not mention the manifest. One more: use an opaque account identifier in the path, not a sequential integer. An integer id is guessable and means nothing outside the platform that minted it. ## Fix the schema, then treat it as a public API Once a partition is loaded, its column names are in somebody's dbt models and somebody else's dashboard. Adding a column at the end is safe. Renaming, reordering or retyping one is a breaking change for every consumer, and it will be discovered weeks later by a number that looks slightly wrong. The hard part is per-tenant custom fields, and the answer is to resist the obvious approach. Do not widen the table with each account's own attribute names: every tenant then has a different table and a shared schema becomes impossible. Put the open-ended parts in a single JSON column. It stays addressable in NDJSON and Parquet, warehouses can query into it, and a new attribute never breaks yesterday's model. Two type details cause quiet damage: - Keep dates separate from timestamps. Rendering a daily counter's date as midnight-in-some-timezone is how a statistic ends up attributed to the wrong day in a warehouse an hour to the left. - Pass the schema explicitly to any native load, never auto-detect. Autodetection infers types per file, so a day where a column happened to be entirely null lands as a different type, and the loads start failing weeks later for no visible reason. ## Say what a partition means Not every dataset partitions the same way, and the difference has to be documented or it will be discovered by a wrong number. - Events partition by when the event happened, taken from the event itself — not by when a batch was archived. Otherwise a late-arriving batch scatters a day across two partitions. - Profiles and visitors are an incremental feed, not a daily snapshot: a record appears in every partition in which it was active, and the newest one holds its newest state. Current state in the warehouse is then a window function over the identifier ordered by last-seen, and stating that up front saves an entire support conversation. - Daily statistics partition by the stat date of the row. ## Generate the load SQL — it is the half people use A bucket full of correct Parquet is still a support ticket if the analyst has to work out the column types, the partition column and the format options by hand. Getting that wrong is how a timestamp silently becomes a string in somebody's model. Write a ready-to-run script beside each partition, generated from the same schema the files were written with — a COPY INTO for Snowflake, a LOAD DATA for BigQuery, a CREATE EXTERNAL TABLE for Athena or Trino. Because it comes from the same source as the data, the two cannot disagree. It is a starting point rather than a migration tool: it names a table, it does not manage one. Where a native load is offered, make it replace a day rather than append to it. Appending doubles every row on the first retry, and the first retry always comes. ## Whose bucket, and why it matters commercially The last decision is not technical. Writing to the customer's own storage, with their credentials, means the storage bill, the retention policy and the residency question are all theirs. It answers the two objections that actually close enterprise deals — "we cannot get our data out" and "we do not want another copy of our data in a vendor's account" — and it costs a vendor nothing except the ability to charge for storage. One practical note if you build it: test the connection by writing a small object and deleting it. A read-only key passes every other check and then fails at 03:00 on a partition nobody is watching. See the datasets, formats and partition ledger on the Warehouse & Storage Export page, or the day-to-day questions the reporting module answers without a warehouse at all. Explore Warehouse Export --- URL: https://www.segmenthub.com/posts/audience-preview-before-you-publish/ - Home Blog Audience Preview Before You Publish Tech • Aug 24, 2026 • 2 min read # Audience Preview Before You Publish A segment definition should be testable. SegmentHub shows who matches, why they match and which rule changed the outcome while the audience is still in the editor. SH SegmentHub Team Product & Engineering Live preview High-intent, no purchase12,840 matches Audience mistakes are expensive because they propagate. A condition that is too broad can send an irrelevant message to thousands of people; one that is too narrow can make a campaign appear broken. Waiting until an audience is saved, synchronized and used in a campaign turns a simple rule problem into an operational investigation. ## Preview the definition, not yesterday's saved version SegmentHub evaluates the rules currently in the editor. That distinction matters: a marketer can change a condition, add an exclusion or select a rolling date and immediately inspect the proposed result without replacing the live audience. The preview returns the number of matching profiles, the total profile population and the calculation time. Masked sample profiles provide recognizable context without exposing raw identifiers in the preview. A zero-match warning catches impossible combinations; a universal or extremely broad warning catches definitions that may be technically valid but operationally risky. ## See what every rule contributes A total count alone cannot explain why the result is surprising. Rule contribution applies the definition cumulatively and shows the count after each condition. Consider a retention audience: - Started with members who viewed a product. - Restricted them to customers seen within the last two weeks. - Excluded anyone who already purchased. If the population collapses at step two, the recency window—not the purchase exclusion—is the first place to investigate. If a rule does not change the count at all, it may be redundant or based on data that is not populated as expected. ## Use real customer context without leaking identifiers Masked sample profiles help answer questions a count cannot: Do the matches look like the intended lifecycle stage? Are expected attributes present? Does a known edge case appear? From the profile view, “why included?” explanations connect the person back to the qualifying audience conditions. ## Rolling dates keep audiences from going stale Fixed dates are useful for one-off analysis. Recurring customer journeys need moving windows such as today, yesterday, one week ago or three months ago. SegmentHub resolves these dynamic values when the rule runs, so “seen within the last two weeks” remains meaningful next month without an editor changing the date. ## A practical pre-publish checklist - Confirm the matched count is plausible relative to the total population. - Review broad, empty and zero-match warnings. - Inspect where the cumulative count changes most sharply. - Check masked samples for the intended customer context. - Compare against an audience already used in market when overlap matters. - Only then save, publish and activate. Audience preview turns segmentation from a configuration exercise into an observable decision. Explore the full workflow on the Audience Intelligence page. Explore Audience Intelligence --- URL: https://www.segmenthub.com/posts/audience-overlap-campaign-cannibalization/ - Home Blog Audience Overlap and Campaign Cannibalization Strategy • Aug 10, 2026 • 2 min read # Audience Overlap and Campaign Cannibalization Two useful audiences can still create a bad customer experience when they contain the same people. Overlap analysis makes that collision visible before launch. SH SegmentHub Team Strategy & Analytics 38% overlap Audience AAudience B Campaign planning often treats audience names as if they describe separate groups. “High-intent visitors,” “loyal members” and “coupon candidates” sound distinct, but customer behavior does not respect campaign labels. One person can qualify for all three. ## What campaign cannibalization looks like Overlap becomes a problem when campaigns compete for the same conversion, bid against each other in advertising platforms, or deliver conflicting incentives. A customer may receive a loyalty-upgrade message and a generic acquisition discount at the same time. The acquisition campaign then takes credit for a conversion the loyalty journey was already likely to produce. The answer is not always to eliminate overlap. The answer is to understand it and choose an explicit policy. ## Read more than one percentage SegmentHub compares two saved audiences and returns five useful values: - Audience A: everyone matching the first definition. - Audience B: everyone matching the second. - Intersection: profiles that qualify for both. - Only A and only B: exclusive reach on each side. - Jaccard overlap: the intersection divided by the combined unique population. A raw intersection of 10,000 may be trivial for two million-person audiences and decisive for two 12,000-person audiences. Jaccard percentage provides the proportional context, while exclusive counts show how much incremental reach remains. ## Four decisions overlap can improve ### 1. Suppression Exclude current customers from acquisition, recent purchasers from cart recovery, or higher-priority lifecycle stages from generic promotions. ### 2. Priority When overlap is intentional, choose which campaign wins. A next-best-action journey should usually outrank a broad seasonal message. ### 3. Media allocation Estimate incremental reach before assigning budgets to similar ad-platform audiences. Large overlap can justify consolidation or a deliberate exclusion structure. ### 4. Measurement Document shared membership before comparing campaign outcomes. Otherwise duplicated exposure can distort attribution and make one campaign appear more incremental than it is. ## A practical review workflow - Preview each audience independently and resolve warnings. - Compare audiences that share a channel, objective or incentive. - Review intersection and exclusive membership—not only audience totals. - Decide whether to suppress, prioritize, consolidate or intentionally allow the overlap. - Record the policy in the campaign setup and revisit it as rolling audiences change. Overlap analysis turns a hidden relationship into a campaign design input. Learn more on the Audience Intelligence page. Compare your audiences --- URL: https://www.segmenthub.com/posts/mobile-push-and-cart-recovery/ - Home Blog Mobile Push and Audience-Aware Cart Recovery Use Case • Jul 27, 2026 • 2 min read # Mobile Push and Audience-Aware Cart Recovery An unfinished cart is a signal, not automatic permission to interrupt. Effective recovery combines cart state, customer eligibility, timing and message-fatigue controls. SH SegmentHub Team Customer Journey Guides Still deciding? Your two saved items are one tap away. Return to cart Basic cart recovery follows a simple rule: cart activity happened, purchase did not, send a reminder. That can recover intent, but it can also message a customer too soon, during the night, after another channel already converted them, or repeatedly across several devices. ## Start with the cart, then qualify the customer SegmentHub keeps the useful cart context—the number of items, total and first item name—then waits for the configured delay. Before producing a notification, it checks whether the cart still qualifies, meets any minimum value, belongs to an eligible customer audience and remains within the per-customer reminder limit. This makes the audience a policy layer. A retailer can target opted-in members, suppress recent purchasers, treat high-value customers differently or limit a campaign to customers whose lifecycle stage makes a reminder appropriate. ## Respect time as part of relevance A technically relevant message can still arrive at the wrong moment. Quiet hours are evaluated in the account timezone. If a campaign becomes due inside that window, SegmentHub postpones it to the end rather than discarding it or sending immediately. Scheduled campaigns use the same timezone-aware principle. One-time sends handle launches and announcements; recurring sends resolve their audience again on each daily, weekly or monthly run; triggered campaigns respond to states such as cart abandonment. ## Choose one reachable device Profiles may contain several device tokens, and tokens may be reassigned as people change or share devices. SegmentHub selects a recently active device per profile, deduplicates shared tokens and skips stale registrations. Jobs are divided into provider-safe batches before delivery. TTL and collapse keys prevent an old or duplicated notification from remaining useful forever. Deep links send the customer directly to the relevant app destination, while image, sound, badge, Android channel and custom data fields support the intended native experience. ## Cap pressure across scheduled messages Frequency limits protect profiles from receiving too many non-triggered pushes in a day. Triggered campaigns retain their own eligibility and reminder controls because a behavioral response should not be treated exactly like a broadcast calendar. ## Measure the delivery chain A campaign is not successful merely because it was scheduled. Reporting should distinguish the profiles that matched, devices that remained reachable, messages sent, provider outcomes, failures and invalid tokens. Invalid registrations are cleaned up so future reports and sends become more accurate. ## Cart recovery checklist - Define the abandonment delay and minimum cart value. - Choose eligible audiences and explicit exclusions. - Set quiet hours and per-customer reminder limits. - Write message variables with safe fallbacks. - Use a deep link that restores the intended cart experience. - Review targeted, sent, failed and invalid-token outcomes. Learn how one-time, recurring and triggered campaigns fit together on the Mobile Push page. Explore Mobile Push --- URL: https://www.segmenthub.com/posts/intent-based-homepage-personalization/ - Home Case Studies Intent-Based Homepage Personalization for İlaçsız Yaşam Use Case • Feb 2, 2026 • 3 min read # Intent-Based Homepage Personalization for İlaçsız Yaşam How SegmentHub dynamically reordered, displayed, and suppressed homepage slides so every visitor saw the opportunity most relevant to their next step. SH SegmentHub Team Customer Success Stories ## Case Study Overview Customer: İlaçsız Yaşam Challenge: A single homepage slider treated new visitors, first-time buyers, loyalty candidates, and established customers as though they needed the same message. Solution: SegmentHub selected, suppressed, and prioritized slides for each visitor using intent, membership, order, profile, and loyalty data. A homepage slider has limited attention to distribute. When every campaign is shown to everyone in the same order, the most valuable position can easily promote an action a visitor has already completed—or one they are not yet ready to take. İlaçsız Yaşam used SegmentHub to turn that fixed sequence into an adaptive customer experience. Instead of asking which campaign should be first for the entire audience, the team could decide which opportunity should be first for each individual. ## One Homepage, Different Customer Intentions SegmentHub combined what was known about the customer with their current stage in the journey. On each visit, it evaluated eligibility rules and changed the slider before presenting the experience. Relevant slides moved forward, lower-priority slides moved back, and ineligible messages were hidden completely. ### New visitors: make the first exchange valuable A visitor without an existing membership relationship saw the “Become a member and get free shipping” campaign. This introduced a clear first step and an immediate benefit without distracting the visitor with loyalty or repeat-purchase messages that did not yet apply. ### Members without an order: remove the first-purchase barrier For a recognized member who had not placed an order, the priority changed to “Place your first order and receive a discount coupon.” SegmentHub knew that registration was already complete, suppressed the redundant membership message, and promoted the next meaningful conversion. ### Members outside the loyalty programme: invite deeper participation When a customer was registered but had not joined the loyalty programme, the homepage could lead with “Become a member of our loyalty programme.” The campaign reached the customers for whom enrollment was both possible and relevant. ### Loyal customers near the next tier: show achievable progress Some loyalty members were only one order away from a higher programme tier. For these customers, SegmentHub prioritized the applicable campaign slide and made the next reward feel immediate. Customers who were not close to an upgrade did not need to see the same urgency. ### Incomplete profiles: exchange value for better data Members with missing profile fields could see “Complete your profile information and receive a free product.” This created a transparent value exchange: the customer received a useful reward, while İlaçsız Yaşam gained the information needed to improve future communication and personalization. ## More Than Reordering Slides The decision was not limited to deciding which slide appeared first. SegmentHub could: - Show a campaign when the visitor met its eligibility conditions. - Hide a campaign after its objective had already been completed. - Reorder eligible campaigns according to the visitor's most likely next action. - Coordinate competing opportunities so the homepage did not deliver contradictory requests. This approach also extends beyond sliders. The same audience and intent rules can select a banner, trigger a popup, or suppress either format when no useful offer is available. The placement changes; the decisioning principle stays the same. The best campaign is not the campaign with the broadest eligibility. It is the one that gives this customer the most relevant reason to take their next step. ## From Campaign Calendar to Customer Decision Traditional homepage planning starts with the campaigns a business wants to promote. Intent-based personalization starts with the customer: What has this person already done? What opportunity are they eligible for? What action would be useful now? By applying those questions in real time, SegmentHub helped İlaçsız Yaşam use the same homepage space for several customer journeys without making the experience feel crowded or generic. SegmentHub knows the customer, evaluates the available opportunities, and chooses the content that fits. Browse More Use Cases --- URL: https://www.segmenthub.com/posts/personalized-search-results/ - Home Case Studies Personalized Search Results: Boosting Conversions for Instreet Use Case • Feb 5, 2025 • 3 min read # Personalized Search Results: Boosting Conversions for Instreet SH SegmentHub Team Customer Success Stories LinkedIn WhatsApp Email ## Case Study Overview Customer: Instreet (A prominent sneaker and sportswear retail chain in Türkiye) Challenge: Enhance the online shopping experience and drive higher conversion rates by transforming generic search results into highly personalized, intent-driven product feeds based on real-time visitor behavior. For leading retail chains like Instreet, which boasts an extensive catalog of top-tier sneaker models and sports products from renowned brands such as Nike, Vans, and Adidas, the search bar is the highest-intent real estate on the website. However, a generic search query like "sneakers" often yields thousands of results. Without personalization, shoppers can experience choice paralysis, leading to abandoned searches and lost revenue. Recognizing this challenge, Instreet aimed to create a frictionless, personalized shopping journey. By integrating SegmentHub, a dynamic Data Management Platform (DMP), Instreet empowered its e-commerce engine to analyze visitor interests in real-time and tailor the search results page (SRP) instantly, significantly boosting customer satisfaction and sales. ## The Scenario The goal was to move away from static, keyword-only search logic and implement a predictive search experience that understands exactly who the user is and what they actually want to buy. ### 1. Active Visitor Engagement The process begins the moment a visitor navigates to Instreet’s online store. Whether they land on the homepage, browse specific categories, or click through a promotional campaign, they begin exploring various sneaker models, activewear, and accessories. ### 2. Real-Time Data Analysis As the user explores the site, SegmentHub operates silently and efficiently in the background. It instantly gathers and synthesizes critical data points to build a comprehensive real-time profile. The platform captures: - Brand Affinity: Which brands (e.g., Nike, Adidas) the user frequently clicks or views. - Demographics & Preferences: Inferred gender and specific color preferences based on product interactions. - Purchasing Power: The average price point of the items the visitor browses. - Size Availability: The shoe or clothing sizes the user has previously selected or filtered. ### 3. Personalized Search Results The true power of this integration shines when the visitor initiates a search. When a user types a broad term like “sneakers” into the search bar, SegmentHub dynamically intercepts and modifies the search results page based on the visitor’s established profile. For example, if the visitor’s browsing history indicates a strong preference for Nike and Adidas, the search algorithm automatically re-ranks the results to prominently feature those brands at the top. If the visitor is identified as female with an affinity for vibrant colors, the results prioritize women’s sizes in those preferred palettes. Furthermore, SegmentHub cross-references stock levels, ensuring the prioritized items are actually available in the user's specific size, eliminating the frustration of out-of-stock discoveries. "By transforming our search engine from a static query tool into a dynamic, intent-driven recommendation engine with SegmentHub, we drastically reduced the path to purchase and delivered a truly bespoke shopping experience." ## Campaign Success & Results Deploying SegmentHub to power personalized search logic proved to be a game-changer for Instreet's e-commerce performance. ### 37% Surge in Search-Driven Sales By prioritizing relevant products, Instreet witnessed a massive leap in conversion rates specifically generated from search traffic. The tailored search results directly led to an impressive 37% boost in sales. Shoppers found what they wanted faster, proving the immense effectiveness of personalized curation in driving bottom-line revenue. ### Enhanced Shopping Experience Visitors were consistently presented with a highly curated selection of sneakers and sportswear that perfectly aligned with their unique preferences. This elimination of digital friction not only increased the immediate likelihood of a purchase but also fostered long-term brand loyalty and higher customer satisfaction. ## Conclusion Through the seamless integration of SegmentHub, Instreet successfully revolutionized its online shopping experience. By abandoning generic search results in favor of real-time data analysis and dynamic content modification, the retailer provided visitors with highly accurate, individualized product recommendations. This strategic pivot resulted in notable improvements in sales performance and customer engagement, firmly positioning Instreet as a market leader in delivering advanced, personalized retail experiences in the Turkish market. Browse More Use Cases --- URL: https://www.segmenthub.com/posts/segmented-smart-banners/ - Home Case Studies Segmented Smart Banners: Enhancing Ad Revenue for BeStyle Use Case • Jan 15, 2025 • 3 min read # Segmented Smart Banners: Enhancing Ad Revenue for BeStyle SH SegmentHub Team Customer Success Stories LinkedIn WhatsApp Email ## Case Study Overview Customer: BeStyle (A prominent tabloid magazine covering lifestyle, beauty, fashion, weddings, and travel topics in Turkiye) Challenge: Enhance its advertising revenue by delivering personalized banners to website visitors based on their interests and content consumption history, seamlessly blending ad placements without disrupting the reader's experience. In the fast-paced world of digital publishing, creating a balance between lucrative ad monetization and a pristine reader experience is a constant challenge. BeStyle, one of Turkiye’s most prominent lifestyle, fashion, and tabloid magazines, needed a way to upgrade its conventional ad inventory. With high daily traffic volumes consisting of users with diverse interests—ranging from wedding planning to luxury travel—relying on static, unsegmented banner ads was leaving significant revenue on the table. To achieve this optimization, BeStyle integrated SegmentHub, a dynamic Data Management Platform (DMP) that analyzes visitor interests in real-time and displays relevant banners tailored strictly to their preferences. ## The Scenario The objective was to move away from generalized placements and serve targeted advertisements based on behavioral signals, essentially curating ads alongside curated editorial content. ### 1. Active Visitor Engagement The journey begins as visitors access the BeStyle website daily to read deep-dive articles or view rich video content. Their sessions span various diverse categories, including lifestyle, beauty, fashion, weddings, or travel topics. ### 2. Real-Time Interest Analysis As users interact with the site, SegmentHub works continuously behind the scenes to monitor and analyze their digital footprints. The platform evaluates: - The specific editorial articles they choose to read (e.g., spending time in the "Beauty" category). - The videos they view and engage with most frequently. - Their overall historical content consumption patterns. This continuous analysis enables SegmentHub to identify explicit interests and current preferences for each individual visitor. ### 3. Segmented Smart Banners For users who have engaged with content on the website, SegmentHub triggers segmented smart banners using its built-in ad server. These banners are dynamically selected based on the visitor’s established interests and content consumption history, ensuring maximum relevance and engagement rather than random ad delivery. "By dynamically shifting our ad strategy from generalized placements to hyper-segmented smart banners with SegmentHub, we transformed empty impressions into high-value engagements that our readers actually care about." ## Campaign Success & Results Through the integration of SegmentHub and the implementation of targeted smart banners, BeStyle successfully revolutionized their digital advertising infrastructure. ### Enhanced Advertising Revenue Visitors browsing BeStyle’s website are presented with personalized banners promoting relevant products or services aligned directly with their interests. By delivering highly targeted advertisements, BeStyle significantly increased the likelihood of click-throughs and conversions. This strategic relevance resulted in a substantial boost in overall advertising revenue. ### Seamless User Experience The personalized approach to banner placement, driven by robust real-time data analysis, naturally enhanced user engagement. Because the relevant ads were delivered in less than 100 milliseconds, the magazine maintained blazing-fast page loads while dramatically improving the effectiveness of their advertising campaigns. ## Conclusion By leveraging SegmentHub’s powerful capabilities to deliver targeted smart banners based on visitors’ real-time interests and content consumption history, BeStyle successfully optimized its overarching digital advertising strategy. The personalized banners not only improved the user experience but consistently increased advertising revenue by serving relevant promotions to website visitors rapidly. This technological integration reaffirms BeStyle’s firm commitment to providing engaging content and maximizing revenue opportunities in the competitive Turkish market. Browse More Use Cases --- URL: https://www.segmenthub.com/posts/targeted-app-install-campaigns/ - Home Case Studies Targeted App Install Campaigns: Driving Mobile Adoption for Sneaks Up Use Case • Dec 10, 2024 • 3 min read # Targeted App Install Campaigns: Driving Mobile Adoption for Sneaks Up SH SegmentHub Team Customer Success Stories LinkedIn WhatsApp Email ## Case Study Overview Customer: Sneaks Up (Leading sneaker and sportswear retailer in Türkiye) Challenge: Increase mobile application installations and foster higher user engagement by capturing the attention of high-intent mobile web visitors through intelligent, personalized banner placements. For major retail brands, native mobile applications are the ultimate driver of customer loyalty and recurring revenue. Sneaks Up, a premier destination for top-tier sneaker models and sports products from brands like Nike, Jordan, and Adidas, recognized that while their mobile web traffic was exceptionally high, their most engaged and profitable customers were shopping inside their native app. To seamlessly transition these mobile web visitors into dedicated app users, Sneaks Up integrated SegmentHub. Leveraging our comprehensive Data Management Platform (DMP) and built-in Ad Server capabilities, the retailer deployed hyper-personalized, targeted app install banners based on real-time visitor behavior. ## The Scenario The primary goal was to move away from generic, intrusive pop-ups and instead deliver contextual app install prompts that enhanced the shopping experience rather than disrupting it. ### 1. Active Visitor Engagement The journey begins the moment a visitor lands on the Sneaks Up website via a mobile browser. Users explore the latest sneaker releases, browse specific sport categories, and compare items across highly sought-after collections. ### 2. Real-Time Interest Identification As the user navigates, SegmentHub works silently in the background, instantly analyzing their browsing journey. It seamlessly gathers data points on: - Specific brand affinities (e.g., heavily viewing the Nike Jordan collection). - Current and historical website interactions. - Previous purchase behaviors and basket sizes. Crucially, the system determines the visitor's device type (mobile web) and checks if the user has previously installed or logged into the Sneaks Up mobile application. ### 3. Targeted Banner Placement For highly engaged mobile web users who do not yet have the app installed, SegmentHub triggers its built-in ad server to deploy segmented app installation banners. Instead of a generic "Download our App" message, the banners are contextually aligned with the user's real-time interest—for instance, displaying an exclusive in-app offer for the exact sneaker brand they are currently browsing. These banners are strategically injected at natural friction points or high-intent moments in the user journey. "By replacing static pop-ups with highly contextual, interest-driven banners powered by SegmentHub, we transformed passive mobile web browsing into a seamless gateway for active app installations." ## Campaign Success & Results Deploying SegmentHub to deliver these behavior-driven app install banners proved transformational for Sneaks Up’s mobile strategy. ### Surge in App Install Rates Because the prompts were displayed exclusively to relevant users (mobile web visitors without the app) and were tailored to their immediate interests, Sneaks Up experienced a dramatic increase in conversion. The targeted approach completely eliminated ad fatigue, ensuring maximum visibility and likelihood of a download. ### Enhanced User Experience & Adoption Shoppers received personalized, value-driven prompts that made downloading the app feel like the logical next step for a superior shopping experience. This frictionless transition not only improved the immediate adoption rate of the mobile application but set the foundation for significantly higher long-term user engagement and lifetime value. ## Conclusion Through the strategic integration of SegmentHub, Sneaks Up successfully optimized its mobile app installation pipeline. By moving away from one-size-fits-all prompts and embracing real-time data analysis, the retailer was able to deliver highly personalized banners based on exact user journeys. This intelligent deployment of targeted advertising not only protected the core user experience but substantially increased app adoption rates, ultimately reinforcing Sneaks Up's position as a forward-thinking, market-leading retailer. Browse More Use Cases --- URL: https://www.segmenthub.com/posts/dmp-vs-cdp-which-do-you-really-need/ - Home Blog DMP vs CDP: Which Do You Really Need? Tech • Dec 5, 2024 • 3 min read # DMP vs CDP: Which Do You Really Need? SH SegmentHub Team Platform Architecture LinkedIn WhatsApp Email Confused by the acronyms? We break down the technical differences between Data Management Platforms (DMP) and Customer Data Platforms (CDP), and why a hybrid approach is winning. If you are building a modern marketing stack, you have likely encountered two heavy hitters: the Customer Data Platform (CDP) and the Data Management Platform (DMP). While they both deal with data and audiences, their architecture, data sources, and primary use cases are completely different. Choosing the wrong one can lead to siloed data, wasted ad spend, and poor customer experiences. Let us decode the differences so you can make an informed decision for your infrastructure. ## What is a DMP (Data Management Platform)? A Data Management Platform is primarily built for the advertising ecosystem. It acts as a data warehouse that sucks in, sorts, and houses information, then spits it out in a way that’s useful for marketers, publishers, and other businesses. - Data Type: Anonymous data (cookies, device IDs, IP addresses). DMPs actively avoid Personally Identifiable Information (PII) like names or emails. - Data Source: Heavily reliant on 3rd-party data bought from data providers, mixed with some 1st-party data. - Storage Duration: Short-term. Data is usually stored for 90 days to capture immediate intent. - Primary Goal: Ad targeting and acquiring new users (Top of Funnel). ## What is a CDP (Customer Data Platform)? A Customer Data Platform is a centralized system that creates a persistent, unified customer database that is accessible to other systems. It is the holy grail for tracking the entire customer journey. - Data Type: Known data (PII). It ties events to specific users using identifiers like emails, phone numbers, or account IDs. - Data Source: Exclusively 1st-party data collected directly from your website, app, CRM, and POS systems. - Storage Duration: Long-term. A CDP builds a historical profile of a customer over years. - Primary Goal: Personalization, retention, customer service, and omni-channel orchestration (Bottom of Funnel & Retention). "A DMP helps you target people who *look* like your customers. A CDP helps you talk directly *to* your customers." ## The Convergence: Why a Hybrid Approach is Winning Historically, companies bought both. The DMP handled acquisition, and the CDP handled retention. But with the death of the third-party cookie and the rise of strict privacy laws (GDPR, CCPA), the traditional DMP model is crumbling. You can no longer rely on anonymous 3rd-party data to fuel your growth. This is why a Hybrid Approach is becoming the industry standard. ### The SegmentHub Advantage SegmentHub acts as a hybrid engine. It functions as a DMP by tracking 100% of anonymous traffic and immediate intent in real-time. The millisecond that user identifies themselves (e.g., signing up), SegmentHub merges that anonymous history into a rich CDP profile. ### The Benefits of a Hybrid Ecosystem - Seamless Identity Resolution: You don't lose the pre-purchase behavioral data once an anonymous visitor creates an account. - Cost Efficiency: Managing two separate enterprise platforms is expensive and requires complex engineering overhead to keep them synced. - Real-Time Activation: A hybrid system allows you to take historical CDP data (e.g., "High LTV Customer") and use it in real-time DMP scenarios (e.g., "Show them a VIP banner on the homepage"). ## The Verdict If you are heavily focused on programmatic advertising and acquiring completely unknown users across the web, you still need DMP functionality. If you are focused on personalizing the experience for your existing user base, you need a CDP. However, if your goal is full-funnel optimization—turning anonymous traffic into known users and known users into loyal advocates—you need a platform that does both natively. Embrace the hybrid architecture, own your 1st-party data, and stop wrestling with acronyms. --- URL: https://www.segmenthub.com/posts/crm-cdp-behavioral-data-enrichment/ - Home Case Studies CRM & CDP Behavioral Data Enrichment: Powering Salesforce with Real-Time Insights Use Case • Nov 14, 2024 • 3 min read # CRM & CDP Behavioral Data Enrichment: Powering Salesforce with Real-Time Insights SH SegmentHub Team Customer Success Stories LinkedIn WhatsApp Email ## Case Study Overview Customer: Prominent E-commerce Company (Confidential) Challenge: Improve the effectiveness of marketing campaigns by overcoming static data limitations and leveraging real-time behavioral insights to enrich their existing Customer Relationship Management (CRM) workflows. In the highly competitive e-commerce landscape, static customer profiles are no longer enough to drive meaningful engagement. A prominent e-commerce company recognized that to significantly improve the effectiveness of its marketing campaigns, it needed to bridge the gap between historical transactional data and active, real-time user intent. By integrating SegmentHub, a dynamic Customer Data Platform (CDP) and Data Management Platform (DMP), the company successfully captured real-time behavioral data and seamlessly enriched its Salesforce CRM, unifying insights across web and mobile touchpoints. ## The Scenario The core objective was to transform dormant customer records into dynamic, actionable profiles. The company deployed SegmentHub to actively analyze visitor behavior and segment users in real-time, subsequently establishing a robust synchronization pipeline to feed these rich insights directly into Salesforce. ### 1. Comprehensive Behavioral Data Collection The foundation of this transformation lay in deep, continuous data collection. SegmentHub was implemented to actively monitor and analyze visitors’ behavioral data as they interacted with the e-commerce platform across both web and mobile devices. This robust tracking included granular details such as: - Detailed browsing history and multi-session navigation paths. - Specific product views, category affinities, and dwell times. - Add-to-cart events, historical purchases, and specific drop-off triggers. ### 2. Dynamic, Real-Time Segmentation Raw data alone is insufficient without context. Based on the collected behavioral inputs, SegmentHub’s processing engine dynamically categorized visitors into highly specific segments in real-time. These segments were not based on broad demographics, but on actual intent and behavior—such as distinguishing between a "window shopper" and a "high-intent returning purchaser." Segment parameters were shaped continuously by browsing patterns, historical purchase velocity, and specific product preferences. ### 3. Seamless Salesforce Synchronization To make these insights actionable for the broader marketing and sales teams, a continuous synchronization pipeline was established between SegmentHub and Salesforce. This seamless data transfer ensured that the CRM database was constantly enriched with the latest behavioral cues. By merging the static transactional and profile information already residing in Salesforce with the real-time behavioral insights generated by SegmentHub, the company achieved a true, dynamic 360-degree view of the customer. "By injecting real-time behavioral data directly into Salesforce, we transformed our static CRM records into dynamic, high-intent profiles, completely revolutionizing how we target and personalize our communications." ## Campaign Success & Results Enriching CRM data with real-time behavioral insights fundamentally strengthened the company’s marketing operations. The integration of SegmentHub with Salesforce led to immediate, significant improvements across the board. ### Elevated Engagement and Conversion Rates By leveraging the newly combined dataset, the marketing team was empowered to deploy highly targeted and profoundly personalized campaigns. Because the messaging was aligned to actual, current user behavior rather than assumed interest, the company achieved substantially higher engagement levels across all communication channels, translating directly into increased conversion rates. ### Driving Business Growth Beyond immediate campaign metrics, this comprehensive understanding of customer behavior fostered deeper loyalty and enhanced overall customer satisfaction. The rich data environment has allowed the company to consistently anticipate customer needs, driving sustainable business growth in a saturated market. ## Conclusion Through the strategic integration of SegmentHub and Salesforce, this prominent e-commerce company successfully enriched its CRM infrastructure with vital, real-time behavioral insights. This capability enabled far more effective targeting and personalization of their marketing campaigns. By leveraging a truly unified dataset, the company maximized its marketing efforts, achieving higher engagement and robust conversion rates. This seamless integration underscores the brand's commitment to adopting advanced, data-driven strategies to continuously enhance the customer experience and secure a competitive edge in the e-commerce sector. Browse More Use Cases --- URL: https://www.segmenthub.com/posts/the-future-of-cookie-less-tracking/ - Home Blog The Future of Cookie-less Tracking Strategy • Oct 24, 2024 • 3 min read # The Future of Cookie-less Tracking SH SegmentHub Team Data Strategy & Privacy LinkedIn WhatsApp Email Chrome did not remove third-party cookies after all — and it changed almost nothing about the direction of travel. Signal loss is already here, it arrived through other doors, and first-party data is still the only durable answer. ## Key takeaways - Google reversed its plan to deprecate third-party cookies in Chrome. The cookie survived; the reliability of cross-site tracking did not. - Safari and Firefox still block third-party cookies by default, and ITP shortens the life of client-side first-party cookies too. - Ad blockers, consent rejection and browser restrictions cause signal loss independently of any Chrome decision. - First-party data collected with consent, unified in a CDP and sent server-side is what still works. ## What actually happened to the third-party cookie For two decades, the third-party cookie was the backbone of the open web. It allowed advertisers to track users across different sites, build detailed profiles, and serve hyper-targeted ads. However, this convenience came at the cost of user privacy. The industry spent years preparing for Chrome to switch it off. Then Google changed course and kept third-party cookies in place rather than deprecating them. If you built a plan around a hard cut-off date, that date never came. It matters far less than it sounds. Safari and Firefox already block third-party cookies by default, and Safari's Intelligent Tracking Prevention also caps how long client-side first-party cookies survive. Add ad blockers, and the share of users who decline consent where regulation requires asking, and the result is the same as it always was: signal loss. Acquisition costs rise as conversion attribution degrades, whatever Chrome does. The lesson is not that the deadline moved. It is that a measurement strategy which depends on any single vendor's roadmap is fragile by construction. "The death of the cookie isn't the death of data. It's the birth of a cleaner, more consensual data relationship." ## Enter First-Party Data The solution isn't a new workaround hack; it's a fundamental shift to First-Party Data. This is data you collect directly from your audience—with their consent. It includes: - Website behavior (pages visited, time on site) - Purchase history - CRM data (email interactions, sales calls) - Survey responses ### Why a CDP is Critical Now Collecting this data is easy. Unifying it is hard. This is where a Customer Data Platform (CDP) like SegmentHub becomes essential. Unlike a DMP (which focuses on anonymous third-party audiences), a CDP unifies data around a persistent customer ID. Pro Tip: Identity Resolution Ensure your CDP has real-time identity resolution. You need to know that the user browsing on mobile is the same user who abandoned a cart on desktop yesterday. ## The Role of Server-Side Tracking Client-side tracking (pixels in the browser) is becoming unreliable due to ad blockers and browser restrictions like ITP. Server-side tracking moves the data collection process from the user's device to your server. This offers three massive benefits: - Data Accuracy: Bypasses ad blockers for 100% visibility. - Performance: Reduces the amount of JavaScript on your site, improving Core Web Vitals. - Control: You decide exactly what data is sent to third parties like Facebook or Google, ensuring better compliance. ## Conclusion The deadline moved; the direction did not. Owning the data relationship - collected with consent, unified around a persistent profile, and sent server-side - is what survives the next reversal as well as this one. The companies that built for that are unaffected by which way Chrome jumps. --- URL: https://www.segmenthub.com/posts/google-ads-data-manage-custom-audience-sync/ - Home Case Studies Google Ads Data Manager: Achieving an 82% Customer Match Rate with Custom Audience Sync Use Case • Jun 4, 2024 • 3 min read # Google Ads Data Manager: Achieving an 82% Customer Match Rate with Custom Audience Sync SH SegmentHub Team Customer Success Stories LinkedIn WhatsApp Email Integration Active ## Case Study Overview Customer: Prominent E-commerce Company (Confidential) Challenge: Enhance targeted advertising by leveraging advanced audience segmentation and synchronization capabilities to combat signal loss and drive campaign efficiency. A leading e-commerce company aimed to enhance its targeted advertising efforts by overhauling its approach to data syndication. Facing industry-wide drops in pixel-based tracking accuracy, the company recognized that leveraging advanced, first-party audience segmentation was the only path forward. By integrating SegmentHub with Google Ads Data Manager, the company sought to achieve higher customer match rates and dramatically improve the efficiency of its marketing campaigns. ## The Scenario The e-commerce brand decided to integrate SegmentHub’s advanced visitor tracking and segmentation platform directly with Google Ads Data Manager. The primary objective was to synchronize custom, high-value audience segments in real-time to Google Ads, allowing for highly targeted and aggressively optimized ad campaigns. ### 1. Comprehensive Data Collection The foundation of this strategy started with clean data. SegmentHub was deployed to track all visitor activities seamlessly across the company’s website and mobile applications. By unifying these cross-device touchpoints, SegmentHub created detailed, persistent user profiles and deep behavioral segments. ### 2. Advanced Audience Building Using SegmentHub’s intuitive Audience Builder, the marketing team began crafting custom audiences based on real-time data flows. Rather than relying on generic demographic buckets, they built dynamic segments based on highly specific attributes such as: - Granular purchasing behavior and historical Lifetime Value (LTV). - Specific product category interests (e.g., users who viewed high-margin electronics more than three times in a week). - Current engagement levels and cart abandonment triggers. ### 3. CRM Enrichment & Real-Time Synchronization To make these profiles even more powerful, the integration pipeline bridged SegmentHub with Salesforce. By enriching CRM data with real-time behavioral insights from the web and app, the company developed a truly comprehensive understanding of customer behavior. These enriched custom audiences were then synchronized directly with Google Ads Data Manager. This seamless flow was achieved through SegmentHub’s robust API and advanced integration functionalities, completely bypassing the need for manual CSV uploads or unreliable browser pixels. "With precise and up-to-date audience segments automatically updating in the background, our performance team was able to deliver highly targeted ad campaigns that drastically improved engagement." ## The Results The integration of SegmentHub with Salesforce and Google Ads Data Manager led to significant, measurable improvements in campaign success for the e-commerce giant. ### Record-Breaking Customer Match Rate Because the data being synced was clean, hashed securely via the server, and rich in identifiers, the integration resulted in a significant increase in the Google Customer Match rate. The company achieved an impressive 82% match rate, which is considered exceptionally high by industry standards. ### Unmatched Efficiency Speed matters in e-commerce. The system handled the synchronization of over 2 million user profiles in under a minute, demonstrating the extreme efficiency and scalability of the SegmentHub integration architecture. ### Enhanced Targeting & Conversion By leveraging a more comprehensive understanding of customer behavior, the company achieved higher engagement levels and increased conversion rates. The precision of the real-time segments meant ad spend was focused exactly where intent was highest, ultimately driving business growth and enhancing customer satisfaction. ## Conclusion Integrating SegmentHub with Google Ads Data Manager enabled this leading e-commerce company to significantly enhance its digital marketing ecosystem. The high customer match rate of 82% and the rapid synchronization of massive user datasets perfectly exemplify the effectiveness of SegmentHub’s data pipeline capabilities. This integration not only immediately improved ad targeting and campaign performance, but it also established a resilient, privacy-compliant data infrastructure that demonstrates massive potential for future growth and optimization in the company’s broader marketing strategies.