Skip to content

Commit

Permalink
callout section changes
Browse files Browse the repository at this point in the history
  • Loading branch information
MaciekVoucherify committed Oct 31, 2023
1 parent 508d248 commit 7366356
Show file tree
Hide file tree
Showing 5 changed files with 41 additions and 9 deletions.
6 changes: 3 additions & 3 deletions docs/guides/integration_blueprint/Data-Model.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ order: 3

# Data model

> 📘 **Goals**
> **Goals**
> * Learn more about metadata.
> * Choose which attributes and events you would like to share with Voucherify.
Expand All @@ -28,15 +28,15 @@ By verifying and defining the data model early by translating data and actions i

The next step is to **plan the frequency of data sync.** Voucherify can work with real-time traffic, which might impact your subscription plan's monthly API call usage.

> 📘
>
>
> Voucherify operates on top of an external master ID (source_id), which lets you sync various pieces of information under a unified ID.
To quickly map out your data model, consider using the ready connectors with [Segment](https://voucherify.io/integrations/segment "Integration with Segment") and [mParticle](https://voucherify.io/integrations/mparticle "Integration with mParticle") CDPs.

For the initial data migration, use asynchronous bulk API import endpoints or upload CSV files in the Dashboard. [Learn more about data integration](https://support.voucherify.io/article/574-data-import "Data Import").

> 📘
>
>
> Voucherify gives you complete control over **how and when to sync data** needed for incentive validation and redemption. You can sync the data before the final stage of the checkout process or send us relevant customer, product, order, and other data right in the validation and redemption requests on the fly.
Expand Down
4 changes: 2 additions & 2 deletions docs/guides/integration_blueprint/Data-Volume-Estimation
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ order: 11

# Data volume estimation

> 📘 **Goals**
> **Goals**
> * Understand what API endpoints will be used to map your scenarios.
> * Estimate how many customers will be included in promotions and how often their data should be synced with Voucherify.
> * Think of what it takes to migrate promotions from your current system.
Expand All @@ -25,7 +25,7 @@ Voucherify works in a [pay-as-you-grow pricing model](https://www.voucherify.io/

Depending on your data volume and/or security policies, your account might require additional activities from the Voucherify team. One of them is setting up **a dedicated cluster near your customers.** This might impact the pricing significantly, so please remember to provide this information to your Technical Integration Manager.

> 📘
>
>
> Besides API usage, you should define your minimum availability requirements. These will be included in a custom SLA.
[Check system status for historical performance >](https://status.voucherify.io/)
4 changes: 2 additions & 2 deletions docs/guides/integration_blueprint/Distributions.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ order: 5

# Distributions

> 📘 **Goals**
> **Goals**
> * Identify which channels should be used for distribution.
> * Learn how Voucherify publication works.
> * Discover Voucherify integrations for messaging.
Expand All @@ -29,6 +29,6 @@ Both push and pull modes can be used with 3rd party platforms.

![3rd party platforms](https://files.readme.io/341f152-guides_integration_blueprint_distributions_3rd_party_platforms.png)

> 📘
>
>
> Publication means incentive assignment. Typically, a publication is performed by sharing codes with customers [via Publication API](ref:publication-object).
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
---
title: Multi-brand management & internationalization
excerpt:
categorySlug: integration-blueprint
slug: brand-management
type: basic
hidden: false
order: 10
---

# Multi-brand management & internationalization

> **Goals**
> * Understand how Voucherify supports multiple brands and locations through projects.

## Outcome:

Ability to set up separate projects for different locations, currencies, brands, or development phases.

Voucherify supports **different approaches to campaign management.** You can use multiple projects to map different contexts or a shared project by using categories, labels, promo code prefixes, or custom fields to differentiate campaigns. Learn how projects can be used to isolate business context and its impact on maintenance and reporting:

* Currency & timezone.
* Users and user roles.
* Email settings & marketing consents.
* Metadata schema.
* Categories.
* API keys, usage & webhooks.

>
>
> Voucherify offers a Management API which allows large teams to manage projects via API, for instance, to set up new projects
under a specific configuration fully programmatically.
4 changes: 2 additions & 2 deletions docs/guides/integration_blueprint/Security.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ order: 12

# Security

> 📘 **Goals**
> **Goals**
> * Learn how Voucherify guarantees campaign security.
> * Identify PII data to be shared with Voucherify.
> * Analyze your distribution processes in relation to GDPR and Data Privacy laws.
Expand Down Expand Up @@ -40,6 +40,6 @@ As an **ISO-27001-certified product**, Voucherify implements several security st

Contact our Customer Success team for a complete **Security Architecture Model** or the recent pentest report.

> 📘
>
>
> If you plan to use Voucherify's built-in messaging, go to a dedicated [GDPR guide](https://support.voucherify.io/article/125-security-data-protection). It showcases how Voucherify implements marketing consents and other requirements from the Directive.

0 comments on commit 7366356

Please sign in to comment.