Everything about finding and verifying contacts.

Run a creator hunt by hashtag, keyword, or follower snowball. Trackyr scrapes public profiles and link-in-bio pages, recovers the email, verifies it, and delivers it with a contactability score. You never export an address that's already bouncing.

Yes. Most creator engines yield email first; toggle reverse-append on the hunt and any contact with a valid email but no number gets a mobile backfilled from a consumer graph, then line-type verified. You're only charged when a number is actually found.

Instagram, TikTok, and YouTube today. Each has its own discovery modes — keyword, hashtag, follower/following snowball, and (on TikTok) post-commenter scraping.

Trackyr's creator engines use logged-out, public-data-only scrapes — the public-data distinction that US courts have repeatedly treated as materially different from login-gated scraping. Every contact stores its provenance — which engine found it, when, and the source URL — and is suppressed across the whole graph within a minute of any opt-out, with deletion requests handled through a public DSAR endpoint.

Every record is re-verified on a rolling cadence, not scraped once and left to rot. Dead numbers and bounced emails are flagged and dropped, so the list you export is contactable today — not the day it was first found.

A fresh verified lead from a hunt is 4 credits; pulling an existing contact from the shared marketplace is free and unlimited on any plan. You pay for the value-add work — discovery and verification — not for re-reading data the pool already holds.

Same core capability — title/industry/company search returning verified work contacts — without the seat-based enterprise pricing or annual lock-in. Trackyr meters usage in credits, pools data so repeat lookups are free, and re-verifies on a rolling cadence instead of selling you a stale snapshot.

Job title, seniority, functional level, industry, company size, location, and revenue/funding. You can also filter by email quality so you only pull contacts above a deliverability threshold.

Both, where available. The B2B engine returns work email and mobile directly; you can also reverse-append a mobile onto any email-only contact and verify its line type before export.

Every contact carries provenance, and opt-outs, bounces, and DNC hits are suppressed across the entire graph within a minute. A public DSAR endpoint intakes right-to-deletion requests handled within the CCPA window, and the contact graph is built to route data-subject requests through the correct regional regime.

A fresh verified lead is 4 credits; pulling an existing contact from the shared pool is free. On the $99 Pro plan that's roughly a few cents per fresh verified contact — well under Apollo's effective per-credit cost.

Each address runs through syntax and MX checks, an SMTP probe, and role-based/disposable filters. Addresses that fail are flagged risky or invalid and excluded from exports, so your bounce rate stays low and your domain stays warm.

Yes. On-demand email verification is 1 credit per address — upload your list and Trackyr returns a valid/risky/invalid verdict per row without re-finding anything.

Yes — creator engines recover personal/business emails from public profiles and link-in-bio pages; the B2B engine returns work emails from an aggregated business database.

Under 2-3% keeps you in good standing with Gmail and Outlook. Because Trackyr drops invalid addresses before export and re-verifies the pool on a cadence, exported lists typically clear that bar without a separate cleaning step.

Yes for B2B — the people search matches a name against the aggregated business database and returns the verified work email. For creators, the finder works from a handle or profile rather than a name, recovering the contact email off the public profile and link-in-bio.

It's the process of finding a phone number from an email address. Trackyr matches a verified email against a consumer phone graph, returns the mobile, and HLR-verifies the line type so you don't waste a send on a landline or dead number.

Every appended number runs through an HLR lookup that reports mobile vs landline vs VOIP and active-status. You can filter to mobile-only before export, which matters for SMS compliance and deliverability.

No. Reverse-append is 6 credits and only charges on a successful, verified match. A miss costs nothing.

Numbers are screened against DNC where applicable, and exports carry TCPA opt-out and quiet-hours metadata your sending tool can enforce. Compliance still depends on your consent posture — Trackyr gives you the verified number and the guardrails, not blanket permission to text.

A phone lookup starts from a number and tells you who owns it. Reverse-append runs the other direction: it starts from a verified email and finds the person's mobile, then line-types it. It's how you add a phone channel to contacts you only had an email for.

Mailbox providers penalize senders with high bounce rates. One dirty campaign can drop your inbox placement for weeks. Verifying before you send keeps bounces low and protects the domain reputation your whole outbound program depends on.

On a rolling cadence — contacts are re-pinged through email and phone validators (never re-scraped) and any record whose every method has gone dead is dropped. You're working from fresh data, not a one-time snapshot.

Yes — on-demand email verify is 1 credit per address and phone verify is 2 credits per number. Upload a list and Trackyr returns per-row verdicts.

Emails come back valid, risky, invalid, or unknown; phones come back with a line type (mobile/landline/VOIP) and active status. You choose the threshold for what makes it into an export.

Yes. Catch-all domains that accept any address are flagged risky rather than passed off as valid, and known disposable and role-based addresses (info@, sales@) are flagged separately so you can decide whether to keep them per campaign.

Run an Instagram hunt by hashtag or keyword and set a follower range to match your tier. Trackyr scrapes public profiles, recovers the business/contact email, verifies it, and delivers it scored — no manual DMing required.

Seed a creator handle and Trackyr discovers the accounts that follow or are followed by it — a fast way to map a tight niche around a known anchor, since a creator's audience and peers are usually in the same vertical.

Some business profiles expose a phone directly; for the rest, toggle reverse-append and Trackyr backfills a verified mobile from the recovered email.

No — Trackyr scrapes logged-out public data on its own infrastructure. You never connect or risk your own Instagram account.

Yes. Set a follower range on the hunt to match your tier — nano and micro creators (1K–25K) for higher reply rates, or larger accounts for reach. Combining a follower range with a hashtag or keyword is the fastest way to isolate a specific niche.

Run a TikTok hunt by keyword or seed handle. Trackyr follows link-in-bio pages, recovers the contact email, and verifies it before delivery.

Point Trackyr at a viral TikTok post and it pulls the accounts that commented — people who self-selected into the topic. It's the highest-intent creator audience you can build because engagement, not just posting, is the signal.

Yes, via reverse-append — TikTok engines yield email, and any email-only contact can have a verified mobile backfilled.

Every contact is re-verified on a rolling cadence, so emails that go dead are dropped from the pool before you export them.

Followers are a passive audience; commenters self-selected by engaging with a specific post. Pulling the commenters on a video that's already performing gives you creators clustered around a proven topic — a tighter, higher-intent list than a broad follower scrape.

Run a YouTube hunt by keyword or channel seed. Trackyr follows the channel's external links — Linktree, Beacons, personal sites — and AI-enriches to surface a contact email, then verifies it.

Most creators gate the email behind a CAPTCHA or omit it entirely, listing only a link hub. Trackyr automates the multi-hop crawl that finding it manually would require, across hundreds of channels at once.

YouTube engines yield email; toggle reverse-append to backfill a verified mobile onto any recovered address.

Hunts are batched — set a result cap and Trackyr works the whole keyword or seed set, delivering verified contacts as they clear validation.

Yes. The crawl doesn't depend on subscriber count — it follows whatever external links a channel lists, so a 2K-subscriber niche creator with a Linktree is just as findable as a million-sub channel. Smaller creators often reply at higher rates.

A verified mobile (via reverse-append), B2B firmographics (company size, industry, revenue, role), and cross-platform handles stitched into a single identity — each field carrying provenance for how it was found.

It's the highest-value enrichment step: a verified email becomes a verified mobile, opening SMS and call channels on a contact you only had an email for. It's 6 credits and only charges on a verified match.

Yes — push a list in, and Trackyr appends verified phones, firmographics, and handles, then exports the completed records back to CSV, a webhook, or your CRM.

Appended methods are re-verified on the same rolling cadence as the rest of the pool, so an enriched record doesn't silently rot after the first pass.

You pay only for the value-add work: reverse-append is 6 credits and charges only on a verified match, email verify is 1 credit, and phone verify is 2. Firmographics and handle-stitching on a contact the pool already holds add no extra credit cost.

Export a column-mapped CSV or fire an outbound webhook into any sequencer or CRM that accepts one — Instantly, Smartlead, GHL, your own endpoint. Pick per-hunt auto-delivery or push a multi-selected batch from the inbox.

Suppressed contacts — opt-outs, bounces, deletions — are filtered out of every export within a minute of being flagged. Exports also carry TCPA opt-out and quiet-hours metadata, so your sending tool can honor it under your own sender identity.

Yes — point a hunt at a webhook and each verified contact is pushed straight through as it clears validation, so leads flow into your sequence without a manual export step.

No — Trackyr is the verified-data layer, not a sender. It hands clean, suppression-filtered contacts to your sending tool of choice, which keeps deliverability and consent under your own sender identity and domain.

A column-mapped CSV with email, phone, line type, contactability score, platform, and provenance per row. A blank-name fill option keeps merge fields from breaking in tools like GHL that have no fallback syntax.

Yes — searching and exporting existing pooled contacts costs zero credits on any plan. Credits only apply to fresh discovery (4), email verify (1), phone verify (2), and reverse-append (6). You're never charged twice for the same contact.

It grows with every hunt run across the platform — creator and B2B contacts in one graph, tagged by niche, role, and platform. The more it fills, the cheaper outreach gets for everyone.

By niche tag, B2B role/industry, platform, geo, contact type (email/phone/both), and contactability score — then export the filtered set to CSV, webhook, or CRM.

Yes — every pooled contact went through verification at discovery and is re-verified on a rolling cadence. Suppressed and dead records are filtered out of every pull.

The pool is the cheapest path when it already holds your niche. A fresh hunt earns its 4 credits when you need a brand-new segment, the latest contacts in a fast-moving niche, or a list no one else has built yet — and whatever it finds drops into the pool for everyone next time.

Creator contacts come from logged-out public profile scrapes; B2B contacts come from an aggregated business-contact database. Every record stores its source URL, scrape timestamp, and the engine that found it.

Under a minute. A suppression entry — from an opt-out, bounce, DNC hit, or DSAR deletion — propagates across the entire shared graph via a database trigger, and every export filters suppressed contacts out automatically.

Through the public DSAR endpoint. Anyone submits a deletion, access, or correction request by email, phone, or handle, and Trackyr processes it within the CCPA 45-day window — matching records are suppressed immediately and removed from the graph as the request is fulfilled.

It's a global do-not-contact layer. Any opt-out, bounce, or DNC entry propagates across the entire shared graph via a database trigger in under a minute, and every export — by any user — filters suppressed contacts out automatically. One suppression protects everyone.

Right-to-deletion requests are handled via the public DSAR endpoint, opt-outs propagate across the graph in under a minute, and creator sourcing is public-data-only with per-record provenance. Trackyr is built data-broker-ready — with jurisdiction-aware request routing and registration planned in key US states as the platform scales.