This pilot explores the way to connect data from two different analytics tools, in this case the usecase is getting past year data from google analytics and current year from adobe analytics. Built on Adobe Serverless platform, this is done using Adobe Analytics API and Google Analytics API
- Populate the
.env
file in the project root and fill it as shown, this includes both Adobe and Google Credentials below
aio app run
to start your local Dev server- App will run on
localhost:9080
by default
By default the UI will be served locally but actions will be deployed and served from Adobe I/O Runtime. To start a
local serverless stack and also run your actions locally use the aio app run --local
option.
- Run
aio app test
to run unit tests for ui and actions - Run
aio app test -e
to run e2e tests
aio app deploy
to build and deploy all actions on Runtime and static files to CDNaio app undeploy
to undeploy the app
# This file must not be committed to source control
## please provide your Adobe I/O Runtime credentials
# AIO_RUNTIME_AUTH=
# AIO_RUNTIME_NAMESPACE=
## please provide your Google Service Accuont Credentials
## to access google data
# GOOGLE_CLIENT_EMAIL=
# GOOGLE_PRIVATE_KEY=
- List your backend actions under the
actions
field within the__APP_PACKAGE__
package placeholder. We will take care of replacing the package name placeholder by your project name and version. - For each action, use the
function
field to indicate the path to the action code. - More documentation for supported action fields can be found here.
-
You have two options to resolve your actions' dependencies:
-
Packaged action file: Add your action's dependencies to the root
package.json
and install them usingnpm install
. Then set thefunction
field inmanifest.yml
to point to the entry file of your action folder. We will useparcelJS
to package your code and dependencies into a single minified js file. The action will then be deployed as a single file. Use this method if you want to reduce the size of your actions. -
Zipped action folder: In the folder containing the action code add a
package.json
with the action's dependencies. Then set thefunction
field inmanifest.yml
to point to the folder of that action. We will install the required dependencies within that directory and zip the folder before deploying it as a zipped action. Use this method if you want to keep your action's dependencies separated.
-
While running your local server (aio app run
), both UI and actions can be debugged, to do so open the vscode debugger
and select the debugging configuration called WebAndActions
.
Alternatively, there are also debug configs for only UI and each separate action.
To use typescript use .tsx
extension for react components and add a tsconfig.json
and make sure you have the below config added
{
"compilerOptions": {
"jsx": "react"
}
}