Is your xDB Cloud Consumption plan right for you ?

When I join my current project first thing I did as architect is an audit.  Make sure that architecture is optimized for current traffic and all best practices has been followed.  The client website use Sitecore xDB Cloud with xDB Plus subscription. It allows you up to 250 000 contacts at anytime and up to 2 500 000 interactions per month.

Contacts

How it’s measured: Total identified contact stored at any time.

Interactions

How it’s measured: Net new interaction created in a given period of time.

I check our current consumption to find out that we can switch to xDB base subscription and pay 30% of what are paying right now.

In some cases you better pay overage price before switch to the next subscription plan.

2017-10-24 11_42_15-xDB - Sales Enablement - March 2015 V2.pptx [Protected View] - PowerPoint

In case you want to generate your own reports or load data directly from mongo, you can access to your xDB database using and mongo viewer application.
Open your connectionstrings.config file and find the “analytics” connection string:
mongodb://{user-name}:{password}@{host1}:{port1},{host2}:{port2}/{guid}-Analytics?ssl=true;replicaSet={hostX}
You have replicaset on XdbCloud so use the host1 and port1 to connect.
Set up values in the following way:

con 2

con 2

But the best approche is to use  sitecore xDB Cloud API

https://gateway-xdb-scs.cloud.sitecore.net/api/xdb/Consumption/licenseId/deploymentId/year/month

where

  • licenseId – your Sitecore license ID
  • deploymentId – the unique identification of the deployment
  • year – the consumption year
  • month – the consumption month

Important

To ensure that your customers only access their own xDB sets, you must use a valid authentication token whenever you make a call to the xDB Cloud API. You can generate these tokens by using a valid Sitecore license file to call the SSO Encode Sitecore License endpoint. You must include the generated token as a HTTP header in all other requests called X-ScS-Nexus-Auth.

Visit this page -> xDB Cloud Consumption