> ## Documentation Index
> Fetch the complete documentation index at: https://docs.authmatech.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Capture Visitor Opportunities with Authmatech Target

> Turn anonymous, high-intent visitors into opportunities your team can re-engage with Authmatech Target — capture sessions, then group and act on them.

Most visitors leave before signing in or completing a purchase. **Authmatech Target** helps you understand and re-engage those customer journeys — so the high-intent customer who left becomes the one you reconnect with. You capture an anonymous visitor's mobile identity signal as an opportunity, then review, group, and act on it from the Client Portal.

## How it works

When the Authmatech SDK runs on a page, it can produce an `authmatechCode` for the visitor's session even before they identify themselves. You send that code — together with your own `metadataId` — to Target, which records it as an opportunity tied to your campaign and context.

```mermaid theme={null}
flowchart LR
    A[Anonymous visitor] --> B[SDK produces authmatechCode]
    B --> C[POST /v1/api/opportunity]
    C --> D[Opportunity recorded]
    D --> E[Review & group in portal]
    E --> F[Re-engage the customer]
```

## Capture an opportunity

Call `POST /v1/api/opportunity` from your backend with the standard `X-API-KEY` + `X-CLIENT-ID` headers.

```bash theme={null}
curl -X POST https://service.authmatech.com/v1/api/opportunity \
  -H "X-API-KEY: YOUR_API_KEY" \
  -H "X-CLIENT-ID: YOUR_CLIENT_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "authmatechCode": "ENCRYPTED_CODE_FROM_SDK",
    "metadataId": "campaign-spring-launch"
  }'
```

<ParamField body="authmatechCode" type="string" required>
  The encrypted identity signal produced by the SDK for the visitor session.
</ParamField>

<ParamField body="metadataId" type="string">
  Your own correlation id — for example a campaign, page, or funnel identifier — echoed back so you can group and report on opportunities.
</ParamField>

For browser flows that resolve the identity from a network transaction, use `POST /v1/api/opportunity/{transactionId}`.

## Review and act on opportunities

Captured opportunities are available through the Client Portal:

| Action             | Endpoint                                 |
| ------------------ | ---------------------------------------- |
| List opportunities | `GET /v1/api/me/opportunities`           |
| Grouped view       | `GET /v1/api/me/opportunities/grouped`   |
| Opportunity stats  | `GET /v1/api/me/opportunities/stats`     |
| Campaign stats     | `GET /v1/api/opportunity/campaign-stats` |

Use the grouped and stats views to see which campaigns and journeys produce the highest-intent visitors, then route them into your re-engagement workflow.

<Note>
  Target is enabled per account. Contact [connect@authmatech.com](mailto:connect@authmatech.com) to turn it on. Always re-engage within your own consent and privacy rules.
</Note>

## Related

<CardGroup cols={2}>
  <Card title="API: Capture an opportunity" icon="code" href="/api/overview">
    Full reference with an interactive playground.
  </Card>

  <Card title="Connect" icon="arrows-rotate" href="/guides/connect">
    Sync opportunities and identity events into your CRM.
  </Card>
</CardGroup>