# Device targets and reusable profiles

A native target identifies an email-client context. A profile saves a target set so a team can repeat the same review without selecting each client for every campaign.

## Discover supported targets

Read the stable target catalog before choosing IDs. Use its client, platform and device metadata to select the contexts your audience uses. The live availability endpoint adds temporary health and queue information; use it to investigate current availability, not to redefine your saved coverage every time a worker is busy.

[API endpoint: `getDevicePreviewTargets`](/docs/api/#getDevicePreviewTargets)

[API endpoint: `getDevicePreviewNativeTargetAvailability`](/docs/api/#getDevicePreviewNativeTargetAvailability)

Use exact catalog IDs in `nativeTargets`. Avoid legacy provider names and reject unknown IDs before running a large batch. Start with a small representative client set and include mobile, desktop or dark-mode variants when they matter to the message.

## Save a profile

1. Open the render-address settings and create a device preview profile.
2. Give it a recognizable name, such as Transactional QA.
3. Choose a local part and the required targets.
4. Send a sample to the profile's render address.
5. Confirm the run contains the expected client set.

See [the dashboard walkthrough](/docs/device-renders/#save-a-reusable-target-profile) for screenshots. For automation, use the profile API:

[API endpoint: `createDevicePreviewProfile`](/docs/api/#createDevicePreviewProfile)

[API endpoint: `getDevicePreviewProfiles`](/docs/api/#getDevicePreviewProfiles)

[API endpoint: `updateDevicePreviewProfile`](/docs/api/#updateDevicePreviewProfile)

## Keep coverage consistent

Review profile changes like other test configuration changes. Record the target set used for a release so a later comparison does not accidentally compare different clients. If a required target fails, inspect or rerun that target; a screenshot from a different client is not replacement evidence.

[CI render checks](/docs/device-rendering-ci/) show how to retain partial evidence while failing an incomplete required run. [Sharing and review](/docs/device-rendering-review/) explains how teammates approve the result.