Core · the software behind TapTech

Run Every Tag, Portal and Audience from One Place

Core is where a brand claims its tags, builds and changes its Portals, and sees everyone who said yes, live. One login, one record, and the record is yours.

Size Core to your programme

core.departmnt.tech
Core: Home

What Core is

One Login, One Audience, One Record

Core is the brand side of TapTech. It shows only the systems you use, and they all share the same audience and the same record, so adding one later needs no new setup.

core.departmnt.tech
Core: Home

From box to live

Five Steps, Most of Them Minutes

What happens between a box of tags arriving and the first person tapping one.

core.departmnt.tech
Core: The box arrives

What it does for you

Set Up, Run, Know, Grow

  1. 01

    Set up

    Tags arrive; Core makes them yours.

    • Claim a batch by its number
    • Point it at a Portal or a page
    • Invite your team

  2. 02

    Run

    Change the moment while it is happening.

    • Edit Portals and journeys live
    • Repoint or switch off any tag
    • Sell tickets and check the door

  3. 03

    Know

    See presence as it lands, not three weeks later.

    • Taps by place and time
    • Who came back, and when
    • Consent kept with every record

  4. 04

    Grow

    Turn the people who came into the people you reach.

    • Segments and campaigns
    • Triggers when something happens
    • Exports, API and webhooks

Where Core sits

Between the Tap and Your Stack

Tags and Portals create the moments. Core turns them into one record and hands it to the tools you already use.

  1. In the world

    Tags

    • Products
    • Places
    • Wrists and passes
    • Packaging and print

    Ten formats, locked. Advance tags are signed on every tap.

  2. In the browser

    Portal

    • Discovery
    • Sign up
    • Feed
    • Hub

    Nineteen modules. No app.

  3. Behind it

    Core

    • Identity and consent
    • Audience
    • Insights
    • Triggers

    One record. Yours.

  4. Out to

    Your stack

    • CRM and email
    • Commerce
    • Analytics
    • API and webhooks

    Exports on every tier; API from Agency.

One moment, followed through · modelled on Genesys TSKO6

  1. Tags21:04

    A wristband is tapped at the door.

  2. Portal21:04

    The ticket opens, checked offline. The holder is in.

  3. Core21:04

    An admit is recorded against a consented person, one scan per ticket.

  4. Your stack21:05

    Core can pass them on as “Came to TSKO6”, ready for the next on sale.

In use

Core, Running Real Work

Modules

Ten Modules Under Everything

Every tier has all ten. What changes is how deep each one goes.

  • Identity

    Tags, owners and the member record.

  • Access

    Who gets in, checked at the door and on the page.

  • Media

    What each Portal delivers, and to whom.

  • Gamify

    Missions, stamps and progression.

  • Connect

    Consent, contact and follow.

  • Trigger

    Automations when something happens.

  • Intel

    Reporting, live and exported.

  • Commerce

    Ticketing and payments. A fee of 3% on Studio and Label, 1.5% on Agency and Network, never added at checkout.

  • Collect

    Collectable objects across moments.

  • Product

    What a product is, and who owns it.

Module depth by tier

Which tier

Size Core to the Programme

How many Portals, people and tags, and for how long. The tool recommends the tier that fits and carries your scope into a brief.

How far back you need the numbers
Use, if you know it

Optional. Adds the ticketing fee and any usage credits past your tier’s allowance.

Selling, tickets, collections, video, music, reminders and page lock come from the modules you chose (from Studio); membership levels, a wallet balance and booking from Label.

Where it stands

Run With You Today, Self Serve Next

  1. Now

    Run with you

    We set up and run Core alongside your team, and you see everything live.

  2. Q4 2026

    Self serve beta

    Selected Base, Studio and Label clients claim batches and build Portals themselves.

  3. 2027

    Full platform launch

    The whole platform, to selected clients, with the API and integrations to match.

FAQs

Who owns the record?

You do. Who took part, what they tapped and what they agreed to sits with you rather than with a platform, and consent is recorded alongside it, so the audience you can contact is a fact rather than an assumption.

Can I change what a tag opens after it ships?

Yes. Re-point a tag, change what a zone opens, or schedule a release, and the hardware in the field stays exactly where it is. That is why the second campaign costs a fraction of the first.

What does it measure, and what does it not?

Presence: a tap, where it happened and when, and whatever someone chose to share after it. It does not follow anybody. Every tap is a person choosing to take part, which is why the count is worth trusting.

Where Next

In the docsCore ↗