Find relevant Shopify prospects for your Klaviyo agency, and know when to reach out.
Find stores worth your agency’s attention and give your business-development team a useful place to start. Shopblips helps you plan a targeted Shopify list, check its available size and choose how many store records to obtain. Your team then uses store identity, supporting details and dates to decide which prospects fit the Klaviyo services you sell. Use available observation dates to help decide when to reach out; first observed is not a launch date, and undated evidence needs a recheck.
Build a prospect list around the service you sell
Your agency chooses the offer, territory, exclusions and review capacity. Shopblips supplies the store-search and record-delivery part of that process. The result your team works toward is a list of distinct stores with a reason to advance, hold or exclude each one.
Start with enough records for a useful prospecting effort, but require usable identity and supporting detail before expanding. A larger list is valuable only when your team can tell which businesses it describes and why they fit. Keep agency need, buying priority and budget as questions for later discovery.
Customer access
Customer store search and purchasing are not open yet. Use this workflow to prepare your selection criteria and review process, and check customer access (under review) before planning a purchase.
Size the segment, then choose a batch your team can review
A count helps you judge the breadth of a supported search before obtaining individual records. It reports overlapping seven-day, 30-day and all-history first-observation windows at the chosen catalog cutoff, with coverage information. It does not deliver store profiles or spend store credits.
Choose the number of profiles to request only after considering the count, its scope and your review capacity. Search delivers full profiles and can use credits. Review the first batch before deciding whether another delivery is worthwhile.
- Define the service and merchant segment. Write the territory, evidence you need and exclusions.
- Use supported country, category and technology criteria where they match that brief. Keep a requirement as a manual review step when it cannot be expressed reliably in the search.
- Inspect the segment count and coverage. Do not treat a catalog count as market-wide adoption or as a list of ready-to-buy clients.
- Choose a small delivery limit and check the available credit balance before requesting records.
- Review the actual records against the same brief, preserve store identity and evidence, then assign a decision and next owner.
Example selection brief: email/SMS management for US beauty merchants
Suppose your agency sells Klaviyo email/SMS management to beauty and personal-care businesses in the United States. That is your chosen service and market. The selection task is to find stores whose territory, sector and dated Klaviyo context support that fit, not to prove their current program needs replacing.
| Agency requirement | Evidence to inspect | How it affects selection |
|---|---|---|
| US territory | The recorded country and its supporting evidence | Use the recorded country and its evidence to assess the agency’s US-market requirement; it is not automatically the merchant’s headquarters. Hold unclear territory fit and exclude a confirmed mismatch. |
| Beauty/personal-care sector | Available category details with their evidence, or a relevant first-party product/catalog source reviewed by your team | Advance this gate only when the actual evidence identifies the sector. An unclear broad category needs review; a confirmed unrelated sector is excluded. |
| Klaviyo context | Technology status, supporting source and observation date | Use a supported dated observation as platform context. Missing support goes on hold; it does not justify calling the store a Klaviyo client. |
| Distinct identity | Store ID, domain and relevant aliases | Keep one research record for the same storefront. Hold unresolved identity before assigning another prospect. |
| Service need | Not established by the search | The seller must confirm program ownership, current priorities and whether an email/SMS management engagement is relevant. |
Optional request details for the same selection brief
For a team using the API, the initial count request is GET /v1/counts?country=US&technology=klaviyo. A bounded first delivery is GET /v1/stores?country=US&technology=klaviyo&limit=5&offset=0. Five is your chosen maximum delivery size, not an available result count.
Category is omitted from these requests. Check the beauty/personal-care requirement from actual category or product evidence unless you have confirmed an appropriate supported category value. To keep the same catalog cutoff, optionally add as_of using the actual URL-encoded value returned by the count. With no narrower first-observation window selected, this request uses all available history; compare it with the count’s all-history total.
Review each delivered store against the beauty-agency brief
The next step is a prospect decision based on the record you actually receive. Keep the criteria unchanged while reviewing a batch so colleagues can understand why one store advanced and another did not.
Decide whether the store supports this service prospect
Advance for agency research only when the store has dependable identity, supported US territory, source-supported beauty/personal-care relevance and dated Klaviyo context. This identifies a research fit, not an agreed need or sales opportunity.
Hold when required identity, sector or technology evidence is missing or unclear. State the missing fact and who will check it. Exclude an actual territory or sector mismatch rather than stretching the agency offer to keep the record.
Validate the Klaviyo context before assigning the next seller
Check the technology entry’s status and evidence. A dated public match helps a Klaviyo specialist identify the systems context to discuss; it does not reveal working flows, account spend or dissatisfaction. Keep an unsupported current-use claim on hold instead of substituting the product name for evidence.
Keep the supporting source beside its observation date
Retain the actual source reference and date with the technology detail so the next researcher can check what it supports. The Klaviyo JavaScript API reference explains the documented onsite-script context; a store’s own evidence must still support its recorded match.
When the technology observation is undated
If its observation-time field (observed_at) is missing, mark that evidence undated. Do not borrow the record’s import, download or last-check date. Assign a recheck before relying on a time-sensitive claim that this store currently uses Klaviyo.
Show the next seller why this store belongs in the list
Manually carry the already-delivered information into your agency’s CRM or research process. Keep the store ID so another person can recognize prior work. The handoff below is a specification for the chosen service; fill its evidence fields only from the actual record and any review your team performs.
| Handoff item | Instruction for this agency brief |
|---|---|
| Identity and existing work | Preserve actual store ID, domain, aliases and any existing CRM/research reference. Check these before creating another prospect. |
| Territory and sector support | Attach the actual evidence supporting US territory and beauty/personal-care relevance. If either is missing, use hold with the missing fact. |
| Platform context | Carry the actual Klaviyo status, supporting source and observation date. Keep undated or unsupported evidence on hold for the intended claim. |
| Reason to advance, if every gate passes | Research fit for the agency’s US beauty/personal-care email/SMS management offer: territory, sector and dated platform context support the segment. Commercial need remains unconfirmed. |
| Decision and responsibility | Record advance, hold or exclude with its reason; assign the researcher or seller responsible and the next evidence check or discovery task. |
| What the next seller must confirm | Who owns the email/SMS program, whether management support is a current priority, which channels and responsibilities are relevant, and whether an appropriate business conversation is welcome. |
Keep the store identity and the age of its evidence useful
The canonical store ID is the stable key for the underlying storefront. Aliases can point to that same store; keep them together so different domain strings do not cause duplicate research. A storefront is not necessarily a separate legal company or CRM account, so your agency still decides the commercial account structure.
First observed means the earliest retained source observation, not the merchant’s launch. Last checked means a check; a later refresh needs its own evidence and may be absent. The catalog cutoff says which information was available for the delivery. Use the date relevant to the question you are asking, rather than assuming one recent date makes every detail current.
Choose the delivery size before spending credits
Each canonical store newly delivered to your account uses one credit, including delivery through search. Later excluding it, or never contacting it, does not undo that debit. Use counts for segment sizing, then choose a profile limit the team can qualify against the service brief.
An authorized same-account reopen costs no additional unique-store credit and returns the previously unlocked frozen copy. It is not fresh enrichment. Aliases do not create a second debit, and changing clients does not create another allowance. Check plans and credit terms before expanding your delivery.
Use the review decisions to improve the next batch
Review why stores advanced, were held or were excluded. If sector evidence is repeatedly missing, decide whether those records are useful for this beauty-agency offer. If the evidence shows unrelated businesses, refine the selection rule. Increasing the profile limit does not resolve either problem automatically.
The agency owns the manual handoff and any later contact process. Shopblips does not automatically sync the list to a CRM, send outreach or open merchants’ Klaviyo accounts. Use the Klaviyo client strategy (under review) when a researched prospect is ready for deeper engagement planning.
Frequently asked questions
How should our agency choose Shopify stores for a Klaviyo service?
Define the service, territory and merchant sector your agency serves. For US beauty/personal-care email/SMS management, require dependable store identity, supported US territory, sector evidence and dated Klaviyo context. Advance records that meet those research gates, hold missing required evidence and exclude confirmed mismatches. Commercial need still requires discovery.
Can we combine Klaviyo with our territory or product category?
Country, category and technology can be combined as search criteria. Use category values the data actually supports. The example starts with US territory and Klaviyo, then checks beauty/personal-care relevance using available category details or your team’s separate first-party product/catalog review. City, proximity, revenue and Klaviyo-spend filters are not supported substitutes for that review.
How can we size a segment before spending profile credits?
Check an authenticated segment count before requesting profiles. It reports overlapping first-observation totals for seven days, 30 days and all available history at the chosen catalog cutoff, with coverage information and no store-credit debit. Then choose how many profiles the team can review. The count shows aggregates; the separate search delivers individual records and can use credits.
How do we avoid paying or researching twice for the same store?
Preserve the canonical store ID and aliases in your CRM or research record, and compare them before assigning another researcher. An authorized reopen of the same underlying store adds no unique-store credit, including an alias match. It returns the frozen copy you unlocked earlier, not refreshed information. Your agency manages the duplicate-work check.
What does a Klaviyo observation tell us about a prospect?
Keep the technology status, supporting source and observation date as platform context for the service question. That helps a Klaviyo specialist decide what systems context to confirm. It does not establish private flow performance, current spend, consent, dissatisfaction or buying intent. A missing observation also does not prove the store never uses Klaviyo.
What should the next researcher or seller receive?
Give them the store ID/domain and aliases, actual territory and sector support, Klaviyo source/date, service-fit reason, unknowns and an advance/hold/exclude decision. Assign a responsible person and next action. For the beauty-agency offer, the next seller must confirm program ownership, relevant management needs and current priority rather than assume a project exists.
Which dates matter when we revisit a prospect?
Use the source date for the detail you rely on and its latest relevant check. First observation is not launch, and a later refresh must be separately evidenced. The catalog cutoff describes the information available for delivery. A free authorized reopen remains the old frozen copy; recheck or hold a current-use claim when its supporting evidence is too old or missing.
When should we request a larger batch?
Expand when actual records support the service brief and the team can review more. First inspect advance, hold and exclusion reasons: missing sector evidence needs a quality decision, while confirmed wrong-sector matches need a selection change. Keep segment counts, delivered stores and qualified accounts separate. None guarantees conversations or revenue.
Does a delivered contact make a store ready for outreach?
Not by itself. Where a contact is present, keep its source and assess its published business purpose and role through your agency’s process. Check prior contact and applicable suppression separately. A store record does not establish decision-maker identity, interest or permission, and Shopblips does not send the message or open the merchant’s account.
Check customer access (under review)