Knowi
내용
[subtitle-meta] lang=en auto=True
If you're running an e-commerce brand,
your data is scattered across a dozen
platforms that don't talk to each other.
Let's fix that in No [music] 'E,
starting with Shopify.
One of the first things you'll do is
connect to your store.
No 'E makes it easy to connect to
Shopify and many other data sources.
We've got native integrations with no
SQL [music] data sources,
SQL databases, data warehouses, [music]
you could bring in Google Sheets or CSV
files,
and lots of cloud services.
If you're running an e-commerce brand,
>> [music]
>> you probably work with a lot of these,
including Instagram, Google Ads, Google
Search Console,
Judge.me Reviews,
Shopify, Recharge.
It's super easy to connect [music] to
your accounts.
For instance, with Shopify, all you have
to do is enter your store domain.
Then you'll authenticate,
and we'll see that we've been generated
an access token, and the authorization
is successful.
From here, I can start querying.
Our visual query builder allows you to
pull in your sales analytics, orders,
customers, [music] products, all of it
in just a few clicks.
So, let me show you some of these.
When you select one of the options to
bring in,
the query will automatically fill
with metrics of [music] interest, so you
can go ahead and preview that and see
your full data set brought directly from
Shopify.
You can also use
these drop-down menus to filter for any
financial or fulfillment status,
and any [music] date ranges you might be
interested in.
Products will show you all of your
different product types [music] on your
store.
You can also pull in customers.
Or you could enter in a specific order
ID to look at that [music] transaction
data.
Let's go ahead and bring in all of our
orders.
If you wanted, you could even run ad hoc
analysis on this data set here
using plain English.
No E's agent automatically analyzes and
filters the data [music] for you to
answer any questions that you ask of
your data set.
So, right now I can see how much we've
got in refunds.
Let's go ahead and bring in our full
data table. So, I'll clear that query.
Under data strategy, I've got a few
options here.
I could run it once and pull in the data
as is, so it's stored in the No E
warehouse.
Or I could run it as a direct query, so
that anytime I open up a dashboard or a
visualization tied to this data [music]
set, I'll pull fresh data from Shopify.
Or I could have my data run on a
scheduled interval.
I'll set this up to run
overnight,
so I'll get fresh data in the morning.
In the data overview page, we can see
the steps we've taken [music] so far.
So, we've got a query with our Shopify
orders. That's generated a nice clean
data set
that we can now build as many dashboards
and [music] widgets or visualizations as
we want.
Now, I don't even have to build a
dashboard myself. I'm going to ask Noe
AI to do it.
I could create it directly from here
using the prompt
or you can go to the AI gigantic agent
[music]
and build a dashboard
from the chat [music] here.
I'm going to keep my ask super broad.
And ask the [music] agent to build a
dashboard showing me how my store is
performing.
The result is a summary of my data set.
So, the agent tells me that the total
revenue across my stores averages just
over $26,000 [music]
with lots of variation between 9,000 to
53,000.
The Snack Shack, [music] which is one of
our brands, leads in sales while Sugar
Bureau lags
suggesting [music] a need to investigate
underperformance.
There's also a section with recommended
actions. Analyze best-selling products
at the Snack Shack to replicate [music]
success in other stores, particularly at
Sugar Bureau, which has the lowest
sales.
Focus on retention strategies and
loyalty programs to capitalize on the
high number of repeat customers. [music]
Let's check out our dashboard.
The data summary is generated at the
top. So, I'll expand [music] that so we
can see it more clearly.
And here we've got total revenue over
time.
We can rearrange [music] these widgets
by dragging and dropping them.
And we can also
go into the tab to verify
the analysis [music] that the AI agent
used
and to change the visualization type.
Another widget on the dashboard is
[music] the recommendations widget.
This will generate findings with
recommended action items for each
insight that the agent finds.
And just like that, we're one step
closer to having all of our e-commerce
metrics in one place. No more juggling a
dozen logins to see how the business is
doing.
원문 자막 펼치기
WEBVTT Kind: captions Language: en 00:00:06.640 --> 00:00:08.510 align:start position:0% If<00:00:06.800><c> you're</c><00:00:07.000><c> running</c><00:00:07.280><c> an</c><00:00:07.440><c> e-commerce</c><00:00:08.000><c> brand,</c> 00:00:08.510 --> 00:00:08.520 align:start position:0% If you're running an e-commerce brand, 00:00:08.520 --> 00:00:10.270 align:start position:0% If you're running an e-commerce brand, your<00:00:08.640><c> data</c><00:00:09.000><c> is</c><00:00:09.120><c> scattered</c><00:00:09.560><c> across</c><00:00:09.840><c> a</c><00:00:09.920><c> dozen</c> 00:00:10.270 --> 00:00:10.280 align:start position:0% your data is scattered across a dozen 00:00:10.280 --> 00:00:12.870 align:start position:0% your data is scattered across a dozen platforms<00:00:10.880><c> that</c><00:00:11.040><c> don't</c><00:00:11.240><c> talk</c><00:00:11.480><c> to</c><00:00:11.600><c> each</c><00:00:11.760><c> other.</c> 00:00:12.870 --> 00:00:12.880 align:start position:0% platforms that don't talk to each other. 00:00:12.880 --> 00:00:13.950 align:start position:0% platforms that don't talk to each other. Let's<00:00:13.080><c> fix</c><00:00:13.320><c> that</c><00:00:13.480><c> in</c><00:00:13.600><c> No</c><00:00:13.755><c> [music]</c><00:00:13.800><c> 'E,</c> 00:00:13.950 --> 00:00:13.960 align:start position:0% Let's fix that in No [music] 'E, 00:00:13.960 --> 00:00:16.310 align:start position:0% Let's fix that in No [music] 'E, starting<00:00:14.360><c> with</c><00:00:14.480><c> Shopify.</c> 00:00:16.310 --> 00:00:16.320 align:start position:0% starting with Shopify. 00:00:16.320 --> 00:00:17.750 align:start position:0% starting with Shopify. One<00:00:16.440><c> of</c><00:00:16.520><c> the</c><00:00:16.640><c> first</c><00:00:16.920><c> things</c><00:00:17.160><c> you'll</c><00:00:17.280><c> do</c><00:00:17.560><c> is</c> 00:00:17.750 --> 00:00:17.760 align:start position:0% One of the first things you'll do is 00:00:17.760 --> 00:00:20.870 align:start position:0% One of the first things you'll do is connect<00:00:18.080><c> to</c><00:00:18.160><c> your</c><00:00:18.280><c> store.</c> 00:00:20.870 --> 00:00:20.880 align:start position:0% 00:00:20.880 --> 00:00:22.270 align:start position:0% No<00:00:21.040><c> 'E</c><00:00:21.120><c> makes</c><00:00:21.400><c> it</c><00:00:21.520><c> easy</c><00:00:21.760><c> to</c><00:00:21.880><c> connect</c><00:00:22.200><c> to</c> 00:00:22.270 --> 00:00:22.280 align:start position:0% No 'E makes it easy to connect to 00:00:22.280 --> 00:00:25.350 align:start position:0% No 'E makes it easy to connect to Shopify<00:00:23.040><c> and</c><00:00:23.240><c> many</c><00:00:23.520><c> other</c><00:00:23.760><c> data</c><00:00:24.040><c> sources.</c> 00:00:25.350 --> 00:00:25.360 align:start position:0% Shopify and many other data sources. 00:00:25.360 --> 00:00:27.390 align:start position:0% Shopify and many other data sources. We've<00:00:25.480><c> got</c><00:00:26.080><c> native</c><00:00:26.400><c> integrations</c><00:00:27.120><c> with</c><00:00:27.240><c> no</c> 00:00:27.390 --> 00:00:27.400 align:start position:0% We've got native integrations with no 00:00:27.400 --> 00:00:29.710 align:start position:0% We've got native integrations with no SQL<00:00:27.510><c> [music]</c><00:00:27.800><c> data</c><00:00:28.040><c> sources,</c> 00:00:29.710 --> 00:00:29.720 align:start position:0% SQL [music] data sources, 00:00:29.720 --> 00:00:33.350 align:start position:0% SQL [music] data sources, SQL<00:00:30.080><c> databases,</c><00:00:31.520><c> data</c><00:00:31.760><c> warehouses,</c><00:00:32.095><c> [music]</c> 00:00:33.350 --> 00:00:33.360 align:start position:0% SQL databases, data warehouses, [music] 00:00:33.360 --> 00:00:35.270 align:start position:0% SQL databases, data warehouses, [music] you<00:00:33.400><c> could</c><00:00:33.560><c> bring</c><00:00:33.760><c> in</c><00:00:33.920><c> Google</c><00:00:34.240><c> Sheets</c><00:00:34.680><c> or</c><00:00:34.760><c> CSV</c> 00:00:35.270 --> 00:00:35.280 align:start position:0% you could bring in Google Sheets or CSV 00:00:35.280 --> 00:00:37.270 align:start position:0% you could bring in Google Sheets or CSV files, 00:00:37.270 --> 00:00:37.280 align:start position:0% files, 00:00:37.280 --> 00:00:39.390 align:start position:0% files, and<00:00:37.400><c> lots</c><00:00:37.640><c> of</c><00:00:37.720><c> cloud</c><00:00:38.040><c> services.</c> 00:00:39.390 --> 00:00:39.400 align:start position:0% and lots of cloud services. 00:00:39.400 --> 00:00:41.255 align:start position:0% and lots of cloud services. If<00:00:39.520><c> you're</c><00:00:39.640><c> running</c><00:00:39.960><c> an</c><00:00:40.080><c> e-commerce</c><00:00:40.600><c> brand,</c> 00:00:41.255 --> 00:00:41.265 align:start position:0% If you're running an e-commerce brand, 00:00:41.265 --> 00:00:41.710 align:start position:0% If you're running an e-commerce brand, >> [music] 00:00:41.710 --> 00:00:41.720 align:start position:0% >> [music] 00:00:41.720 --> 00:00:43.590 align:start position:0% >> [music] >> you<00:00:41.840><c> probably</c><00:00:42.280><c> work</c><00:00:42.480><c> with</c><00:00:42.640><c> a</c><00:00:42.680><c> lot</c><00:00:42.880><c> of</c><00:00:42.960><c> these,</c> 00:00:43.590 --> 00:00:43.600 align:start position:0% >> you probably work with a lot of these, 00:00:43.600 --> 00:00:46.470 align:start position:0% >> you probably work with a lot of these, including<00:00:44.120><c> Instagram,</c><00:00:45.080><c> Google</c><00:00:45.520><c> Ads,</c><00:00:46.200><c> Google</c> 00:00:46.470 --> 00:00:46.480 align:start position:0% including Instagram, Google Ads, Google 00:00:46.480 --> 00:00:48.030 align:start position:0% including Instagram, Google Ads, Google Search<00:00:46.800><c> Console,</c> 00:00:48.030 --> 00:00:48.040 align:start position:0% Search Console, 00:00:48.040 --> 00:00:50.350 align:start position:0% Search Console, Judge.me<00:00:48.480><c> Reviews,</c> 00:00:50.350 --> 00:00:50.360 align:start position:0% Judge.me Reviews, 00:00:50.360 --> 00:00:52.950 align:start position:0% Judge.me Reviews, Shopify,<00:00:51.400><c> Recharge.</c> 00:00:52.950 --> 00:00:52.960 align:start position:0% Shopify, Recharge. 00:00:52.960 --> 00:00:54.510 align:start position:0% Shopify, Recharge. It's<00:00:53.080><c> super</c><00:00:53.360><c> easy</c><00:00:53.920><c> to</c><00:00:54.040><c> connect</c><00:00:54.365><c> [music]</c><00:00:54.440><c> to</c> 00:00:54.510 --> 00:00:54.520 align:start position:0% It's super easy to connect [music] to 00:00:54.520 --> 00:00:56.190 align:start position:0% It's super easy to connect [music] to your<00:00:54.680><c> accounts.</c> 00:00:56.190 --> 00:00:56.200 align:start position:0% your accounts. 00:00:56.200 --> 00:00:58.070 align:start position:0% your accounts. For<00:00:56.240><c> instance,</c><00:00:56.760><c> with</c><00:00:56.840><c> Shopify,</c><00:00:57.760><c> all</c><00:00:57.920><c> you</c><00:00:57.960><c> have</c> 00:00:58.070 --> 00:00:58.080 align:start position:0% For instance, with Shopify, all you have 00:00:58.080 --> 00:01:03.390 align:start position:0% For instance, with Shopify, all you have to<00:00:58.200><c> do</c><00:00:58.440><c> is</c><00:00:58.560><c> enter</c><00:00:58.840><c> your</c><00:00:58.960><c> store</c><00:00:59.280><c> domain.</c> 00:01:03.390 --> 00:01:03.400 align:start position:0% 00:01:03.400 --> 00:01:08.870 align:start position:0% Then<00:01:03.560><c> you'll</c><00:01:03.720><c> authenticate,</c> 00:01:08.870 --> 00:01:08.880 align:start position:0% 00:01:08.880 --> 00:01:10.390 align:start position:0% and<00:01:09.000><c> we'll</c><00:01:09.120><c> see</c><00:01:09.280><c> that</c><00:01:09.400><c> we've</c><00:01:09.600><c> been</c><00:01:09.880><c> generated</c> 00:01:10.390 --> 00:01:10.400 align:start position:0% and we'll see that we've been generated 00:01:10.400 --> 00:01:12.470 align:start position:0% and we'll see that we've been generated an<00:01:10.560><c> access</c><00:01:10.960><c> token,</c><00:01:11.440><c> and</c><00:01:11.560><c> the</c><00:01:11.640><c> authorization</c> 00:01:12.470 --> 00:01:12.480 align:start position:0% an access token, and the authorization 00:01:12.480 --> 00:01:16.950 align:start position:0% an access token, and the authorization is<00:01:12.640><c> successful.</c> 00:01:16.950 --> 00:01:16.960 align:start position:0% 00:01:16.960 --> 00:01:20.670 align:start position:0% From<00:01:17.120><c> here,</c><00:01:17.400><c> I</c><00:01:17.440><c> can</c><00:01:17.600><c> start</c><00:01:17.880><c> querying.</c> 00:01:20.670 --> 00:01:20.680 align:start position:0% 00:01:20.680 --> 00:01:22.390 align:start position:0% Our<00:01:20.800><c> visual</c><00:01:21.160><c> query</c><00:01:21.440><c> builder</c><00:01:21.840><c> allows</c><00:01:22.200><c> you</c><00:01:22.280><c> to</c> 00:01:22.390 --> 00:01:22.400 align:start position:0% Our visual query builder allows you to 00:01:22.400 --> 00:01:25.230 align:start position:0% Our visual query builder allows you to pull<00:01:22.720><c> in</c><00:01:22.960><c> your</c><00:01:23.080><c> sales</c><00:01:23.480><c> analytics,</c><00:01:24.560><c> orders,</c> 00:01:25.230 --> 00:01:25.240 align:start position:0% pull in your sales analytics, orders, 00:01:25.240 --> 00:01:27.670 align:start position:0% pull in your sales analytics, orders, customers,<00:01:25.805><c> [music]</c><00:01:26.080><c> products,</c><00:01:27.160><c> all</c><00:01:27.360><c> of</c><00:01:27.480><c> it</c> 00:01:27.670 --> 00:01:27.680 align:start position:0% customers, [music] products, all of it 00:01:27.680 --> 00:01:29.390 align:start position:0% customers, [music] products, all of it in<00:01:27.800><c> just</c><00:01:28.040><c> a</c><00:01:28.080><c> few</c><00:01:28.280><c> clicks.</c> 00:01:29.390 --> 00:01:29.400 align:start position:0% in just a few clicks. 00:01:29.400 --> 00:01:32.190 align:start position:0% in just a few clicks. So,<00:01:29.440><c> let</c><00:01:29.520><c> me</c><00:01:29.600><c> show</c><00:01:29.760><c> you</c><00:01:29.880><c> some</c><00:01:30.000><c> of</c><00:01:30.080><c> these.</c> 00:01:32.190 --> 00:01:32.200 align:start position:0% So, let me show you some of these. 00:01:32.200 --> 00:01:33.990 align:start position:0% So, let me show you some of these. When<00:01:32.320><c> you</c><00:01:32.400><c> select</c><00:01:33.000><c> one</c><00:01:33.200><c> of</c><00:01:33.280><c> the</c><00:01:33.400><c> options</c><00:01:33.920><c> to</c> 00:01:33.990 --> 00:01:34.000 align:start position:0% When you select one of the options to 00:01:34.000 --> 00:01:35.750 align:start position:0% When you select one of the options to bring<00:01:34.280><c> in,</c> 00:01:35.750 --> 00:01:35.760 align:start position:0% bring in, 00:01:35.760 --> 00:01:38.270 align:start position:0% bring in, the<00:01:35.840><c> query</c><00:01:36.200><c> will</c><00:01:36.440><c> automatically</c><00:01:37.160><c> fill</c> 00:01:38.270 --> 00:01:38.280 align:start position:0% the query will automatically fill 00:01:38.280 --> 00:01:39.790 align:start position:0% the query will automatically fill with<00:01:38.480><c> metrics</c><00:01:38.880><c> of</c><00:01:38.906><c> [music]</c><00:01:39.000><c> interest,</c><00:01:39.600><c> so</c><00:01:39.720><c> you</c> 00:01:39.790 --> 00:01:39.800 align:start position:0% with metrics of [music] interest, so you 00:01:39.800 --> 00:01:41.630 align:start position:0% with metrics of [music] interest, so you can<00:01:39.920><c> go</c><00:01:40.080><c> ahead</c><00:01:40.320><c> and</c><00:01:40.440><c> preview</c><00:01:40.840><c> that</c><00:01:41.240><c> and</c><00:01:41.440><c> see</c> 00:01:41.630 --> 00:01:41.640 align:start position:0% can go ahead and preview that and see 00:01:41.640 --> 00:01:43.950 align:start position:0% can go ahead and preview that and see your<00:01:41.800><c> full</c><00:01:42.040><c> data</c><00:01:42.320><c> set</c><00:01:42.960><c> brought</c><00:01:43.200><c> directly</c><00:01:43.680><c> from</c> 00:01:43.950 --> 00:01:43.960 align:start position:0% your full data set brought directly from 00:01:43.960 --> 00:01:47.830 align:start position:0% your full data set brought directly from Shopify. 00:01:47.830 --> 00:01:47.840 align:start position:0% 00:01:47.840 --> 00:01:49.630 align:start position:0% You<00:01:47.920><c> can</c><00:01:48.040><c> also</c><00:01:48.440><c> use</c> 00:01:49.630 --> 00:01:49.640 align:start position:0% You can also use 00:01:49.640 --> 00:01:52.070 align:start position:0% You can also use these<00:01:49.840><c> drop-down</c><00:01:50.360><c> menus</c><00:01:51.000><c> to</c><00:01:51.160><c> filter</c><00:01:51.760><c> for</c><00:01:51.880><c> any</c> 00:01:52.070 --> 00:01:52.080 align:start position:0% these drop-down menus to filter for any 00:01:52.080 --> 00:01:54.950 align:start position:0% these drop-down menus to filter for any financial<00:01:52.920><c> or</c><00:01:53.040><c> fulfillment</c><00:01:53.600><c> status,</c> 00:01:54.950 --> 00:01:54.960 align:start position:0% financial or fulfillment status, 00:01:54.960 --> 00:01:56.430 align:start position:0% financial or fulfillment status, and<00:01:55.240><c> any</c><00:01:55.281><c> [music]</c><00:01:55.440><c> date</c><00:01:55.680><c> ranges</c><00:01:56.080><c> you</c><00:01:56.160><c> might</c><00:01:56.320><c> be</c> 00:01:56.430 --> 00:01:56.440 align:start position:0% and any [music] date ranges you might be 00:01:56.440 --> 00:02:06.910 align:start position:0% and any [music] date ranges you might be interested<00:01:57.000><c> in.</c> 00:02:06.910 --> 00:02:06.920 align:start position:0% 00:02:06.920 --> 00:02:08.230 align:start position:0% Products<00:02:07.360><c> will</c><00:02:07.479><c> show</c><00:02:07.680><c> you</c><00:02:07.840><c> all</c><00:02:08.039><c> of</c><00:02:08.119><c> your</c> 00:02:08.230 --> 00:02:08.240 align:start position:0% Products will show you all of your 00:02:08.240 --> 00:02:09.469 align:start position:0% Products will show you all of your different<00:02:08.560><c> product</c><00:02:08.920><c> types</c><00:02:09.036><c> [music]</c><00:02:09.280><c> on</c><00:02:09.360><c> your</c> 00:02:09.469 --> 00:02:09.479 align:start position:0% different product types [music] on your 00:02:09.479 --> 00:02:15.150 align:start position:0% different product types [music] on your store. 00:02:15.150 --> 00:02:15.160 align:start position:0% 00:02:15.160 --> 00:02:25.310 align:start position:0% You<00:02:15.240><c> can</c><00:02:15.360><c> also</c><00:02:15.640><c> pull</c><00:02:15.920><c> in</c><00:02:16.040><c> customers.</c> 00:02:25.310 --> 00:02:25.320 align:start position:0% 00:02:25.320 --> 00:02:27.230 align:start position:0% Or<00:02:25.640><c> you</c><00:02:25.800><c> could</c><00:02:26.000><c> enter</c><00:02:26.280><c> in</c><00:02:26.360><c> a</c><00:02:26.400><c> specific</c><00:02:26.959><c> order</c> 00:02:27.230 --> 00:02:27.240 align:start position:0% Or you could enter in a specific order 00:02:27.240 --> 00:02:29.150 align:start position:0% Or you could enter in a specific order ID<00:02:27.600><c> to</c><00:02:27.760><c> look</c><00:02:27.920><c> at</c><00:02:28.000><c> that</c><00:02:28.031><c> [music]</c><00:02:28.520><c> transaction</c> 00:02:29.150 --> 00:02:29.160 align:start position:0% ID to look at that [music] transaction 00:02:29.160 --> 00:02:30.750 align:start position:0% ID to look at that [music] transaction data. 00:02:30.750 --> 00:02:30.760 align:start position:0% data. 00:02:30.760 --> 00:02:32.110 align:start position:0% data. Let's<00:02:30.920><c> go</c><00:02:31.000><c> ahead</c><00:02:31.240><c> and</c><00:02:31.360><c> bring</c><00:02:31.560><c> in</c><00:02:31.680><c> all</c><00:02:31.880><c> of</c><00:02:31.959><c> our</c> 00:02:32.110 --> 00:02:32.120 align:start position:0% Let's go ahead and bring in all of our 00:02:32.120 --> 00:02:34.510 align:start position:0% Let's go ahead and bring in all of our orders. 00:02:34.510 --> 00:02:34.520 align:start position:0% orders. 00:02:34.520 --> 00:02:36.350 align:start position:0% orders. If<00:02:34.640><c> you</c><00:02:34.760><c> wanted,</c><00:02:35.240><c> you</c><00:02:35.320><c> could</c><00:02:35.520><c> even</c><00:02:35.760><c> run</c><00:02:36.000><c> ad</c><00:02:36.200><c> hoc</c> 00:02:36.350 --> 00:02:36.360 align:start position:0% If you wanted, you could even run ad hoc 00:02:36.360 --> 00:02:39.070 align:start position:0% If you wanted, you could even run ad hoc analysis<00:02:37.080><c> on</c><00:02:37.280><c> this</c><00:02:37.400><c> data</c><00:02:37.680><c> set</c><00:02:37.920><c> here</c> 00:02:39.070 --> 00:02:39.080 align:start position:0% analysis on this data set here 00:02:39.080 --> 00:02:44.310 align:start position:0% analysis on this data set here using<00:02:39.400><c> plain</c><00:02:39.640><c> English.</c> 00:02:44.310 --> 00:02:44.320 align:start position:0% 00:02:44.320 --> 00:02:46.990 align:start position:0% No<00:02:44.520><c> E's</c><00:02:44.840><c> agent</c><00:02:45.280><c> automatically</c><00:02:46.200><c> analyzes</c><00:02:46.880><c> and</c> 00:02:46.990 --> 00:02:47.000 align:start position:0% No E's agent automatically analyzes and 00:02:47.000 --> 00:02:48.270 align:start position:0% No E's agent automatically analyzes and filters<00:02:47.400><c> the</c><00:02:47.480><c> data</c><00:02:47.681><c> [music]</c><00:02:47.760><c> for</c><00:02:48.040><c> you</c><00:02:48.160><c> to</c> 00:02:48.270 --> 00:02:48.280 align:start position:0% filters the data [music] for you to 00:02:48.280 --> 00:02:49.750 align:start position:0% filters the data [music] for you to answer<00:02:48.600><c> any</c><00:02:48.800><c> questions</c><00:02:49.240><c> that</c><00:02:49.360><c> you</c><00:02:49.440><c> ask</c><00:02:49.680><c> of</c> 00:02:49.750 --> 00:02:49.760 align:start position:0% answer any questions that you ask of 00:02:49.760 --> 00:02:51.150 align:start position:0% answer any questions that you ask of your<00:02:49.880><c> data</c><00:02:50.120><c> set.</c> 00:02:51.150 --> 00:02:51.160 align:start position:0% your data set. 00:02:51.160 --> 00:02:52.750 align:start position:0% your data set. So,<00:02:51.240><c> right</c><00:02:51.400><c> now</c><00:02:51.640><c> I</c><00:02:51.720><c> can</c><00:02:51.880><c> see</c><00:02:52.120><c> how</c><00:02:52.320><c> much</c><00:02:52.600><c> we've</c> 00:02:52.750 --> 00:02:52.760 align:start position:0% So, right now I can see how much we've 00:02:52.760 --> 00:02:56.150 align:start position:0% So, right now I can see how much we've got<00:02:53.040><c> in</c><00:02:53.200><c> refunds.</c> 00:02:56.150 --> 00:02:56.160 align:start position:0% 00:02:56.160 --> 00:02:57.470 align:start position:0% Let's<00:02:56.320><c> go</c><00:02:56.440><c> ahead</c><00:02:56.640><c> and</c><00:02:56.760><c> bring</c><00:02:56.959><c> in</c><00:02:57.120><c> our</c><00:02:57.240><c> full</c> 00:02:57.470 --> 00:02:57.480 align:start position:0% Let's go ahead and bring in our full 00:02:57.480 --> 00:03:01.830 align:start position:0% Let's go ahead and bring in our full data<00:02:57.760><c> table.</c><00:02:58.440><c> So,</c><00:02:58.640><c> I'll</c><00:02:58.760><c> clear</c><00:02:59.080><c> that</c><00:02:59.440><c> query.</c> 00:03:01.830 --> 00:03:01.840 align:start position:0% data table. So, I'll clear that query. 00:03:01.840 --> 00:03:03.470 align:start position:0% data table. So, I'll clear that query. Under<00:03:02.000><c> data</c><00:03:02.280><c> strategy,</c><00:03:02.920><c> I've</c><00:03:03.040><c> got</c><00:03:03.200><c> a</c><00:03:03.239><c> few</c> 00:03:03.470 --> 00:03:03.480 align:start position:0% Under data strategy, I've got a few 00:03:03.480 --> 00:03:04.830 align:start position:0% Under data strategy, I've got a few options<00:03:03.920><c> here.</c> 00:03:04.830 --> 00:03:04.840 align:start position:0% options here. 00:03:04.840 --> 00:03:06.790 align:start position:0% options here. I<00:03:04.920><c> could</c><00:03:05.239><c> run</c><00:03:05.400><c> it</c><00:03:05.519><c> once</c><00:03:05.880><c> and</c><00:03:06.040><c> pull</c><00:03:06.239><c> in</c><00:03:06.360><c> the</c><00:03:06.440><c> data</c> 00:03:06.790 --> 00:03:06.800 align:start position:0% I could run it once and pull in the data 00:03:06.800 --> 00:03:08.830 align:start position:0% I could run it once and pull in the data as<00:03:07.080><c> is,</c><00:03:07.440><c> so</c><00:03:07.640><c> it's</c><00:03:07.840><c> stored</c><00:03:08.239><c> in</c><00:03:08.320><c> the</c><00:03:08.400><c> No</c><00:03:08.600><c> E</c> 00:03:08.830 --> 00:03:08.840 align:start position:0% as is, so it's stored in the No E 00:03:08.840 --> 00:03:10.470 align:start position:0% as is, so it's stored in the No E warehouse. 00:03:10.470 --> 00:03:10.480 align:start position:0% warehouse. 00:03:10.480 --> 00:03:12.790 align:start position:0% warehouse. Or<00:03:10.680><c> I</c><00:03:10.720><c> could</c><00:03:10.880><c> run</c><00:03:11.040><c> it</c><00:03:11.160><c> as</c><00:03:11.280><c> a</c><00:03:11.320><c> direct</c><00:03:11.720><c> query,</c><00:03:12.680><c> so</c> 00:03:12.790 --> 00:03:12.800 align:start position:0% Or I could run it as a direct query, so 00:03:12.800 --> 00:03:14.910 align:start position:0% Or I could run it as a direct query, so that<00:03:12.959><c> anytime</c><00:03:13.440><c> I</c><00:03:13.480><c> open</c><00:03:13.720><c> up</c><00:03:13.840><c> a</c><00:03:13.920><c> dashboard</c><00:03:14.680><c> or</c><00:03:14.880><c> a</c> 00:03:14.910 --> 00:03:14.920 align:start position:0% that anytime I open up a dashboard or a 00:03:14.920 --> 00:03:16.550 align:start position:0% that anytime I open up a dashboard or a visualization<00:03:15.800><c> tied</c><00:03:16.080><c> to</c><00:03:16.160><c> this</c><00:03:16.280><c> data</c><00:03:16.502><c> [music]</c> 00:03:16.550 --> 00:03:16.560 align:start position:0% visualization tied to this data [music] 00:03:16.560 --> 00:03:21.310 align:start position:0% visualization tied to this data [music] set,<00:03:17.480><c> I'll</c><00:03:17.640><c> pull</c><00:03:17.840><c> fresh</c><00:03:18.160><c> data</c><00:03:18.480><c> from</c><00:03:18.680><c> Shopify.</c> 00:03:21.310 --> 00:03:21.320 align:start position:0% set, I'll pull fresh data from Shopify. 00:03:21.320 --> 00:03:22.630 align:start position:0% set, I'll pull fresh data from Shopify. Or<00:03:21.480><c> I</c><00:03:21.560><c> could</c><00:03:21.680><c> have</c><00:03:21.840><c> my</c><00:03:21.959><c> data</c><00:03:22.280><c> run</c><00:03:22.519><c> on</c><00:03:22.600><c> a</c> 00:03:22.630 --> 00:03:22.640 align:start position:0% Or I could have my data run on a 00:03:22.640 --> 00:03:25.310 align:start position:0% Or I could have my data run on a scheduled<00:03:23.120><c> interval.</c> 00:03:25.310 --> 00:03:25.320 align:start position:0% scheduled interval. 00:03:25.320 --> 00:03:28.229 align:start position:0% scheduled interval. I'll<00:03:25.519><c> set</c><00:03:25.720><c> this</c><00:03:25.880><c> up</c><00:03:26.040><c> to</c><00:03:26.200><c> run</c> 00:03:28.229 --> 00:03:28.239 align:start position:0% I'll set this up to run 00:03:28.239 --> 00:03:30.430 align:start position:0% I'll set this up to run overnight, 00:03:30.430 --> 00:03:30.440 align:start position:0% overnight, 00:03:30.440 --> 00:03:42.150 align:start position:0% overnight, so<00:03:30.519><c> I'll</c><00:03:30.640><c> get</c><00:03:30.800><c> fresh</c><00:03:31.040><c> data</c><00:03:31.360><c> in</c><00:03:31.440><c> the</c><00:03:31.519><c> morning.</c> 00:03:42.150 --> 00:03:42.160 align:start position:0% 00:03:42.160 --> 00:03:43.830 align:start position:0% In<00:03:42.239><c> the</c><00:03:42.360><c> data</c><00:03:42.680><c> overview</c><00:03:43.080><c> page,</c><00:03:43.480><c> we</c><00:03:43.600><c> can</c><00:03:43.720><c> see</c> 00:03:43.830 --> 00:03:43.840 align:start position:0% In the data overview page, we can see 00:03:43.840 --> 00:03:46.150 align:start position:0% In the data overview page, we can see the<00:03:43.959><c> steps</c><00:03:44.320><c> we've</c><00:03:44.480><c> taken</c><00:03:44.667><c> [music]</c><00:03:44.840><c> so</c><00:03:45.040><c> far.</c> 00:03:46.150 --> 00:03:46.160 align:start position:0% the steps we've taken [music] so far. 00:03:46.160 --> 00:03:47.870 align:start position:0% the steps we've taken [music] so far. So,<00:03:46.239><c> we've</c><00:03:46.400><c> got</c><00:03:46.560><c> a</c><00:03:46.640><c> query</c><00:03:47.080><c> with</c><00:03:47.239><c> our</c><00:03:47.320><c> Shopify</c> 00:03:47.870 --> 00:03:47.880 align:start position:0% So, we've got a query with our Shopify 00:03:47.880 --> 00:03:51.190 align:start position:0% So, we've got a query with our Shopify orders.<00:03:48.959><c> That's</c><00:03:49.239><c> generated</c><00:03:50.560><c> a</c><00:03:50.600><c> nice</c><00:03:50.920><c> clean</c> 00:03:51.190 --> 00:03:51.200 align:start position:0% orders. That's generated a nice clean 00:03:51.200 --> 00:03:52.870 align:start position:0% orders. That's generated a nice clean data<00:03:51.480><c> set</c> 00:03:52.870 --> 00:03:52.880 align:start position:0% data set 00:03:52.880 --> 00:03:55.110 align:start position:0% data set that<00:03:53.000><c> we</c><00:03:53.120><c> can</c><00:03:53.280><c> now</c><00:03:53.560><c> build</c><00:03:53.880><c> as</c><00:03:53.960><c> many</c><00:03:54.200><c> dashboards</c> 00:03:55.110 --> 00:03:55.120 align:start position:0% that we can now build as many dashboards 00:03:55.120 --> 00:03:57.110 align:start position:0% that we can now build as many dashboards and<00:03:55.147><c> [music]</c><00:03:55.400><c> widgets</c><00:03:55.880><c> or</c><00:03:56.000><c> visualizations</c><00:03:56.960><c> as</c> 00:03:57.110 --> 00:03:57.120 align:start position:0% and [music] widgets or visualizations as 00:03:57.120 --> 00:04:00.470 align:start position:0% and [music] widgets or visualizations as we<00:03:57.240><c> want.</c> 00:04:00.470 --> 00:04:00.480 align:start position:0% 00:04:00.480 --> 00:04:01.910 align:start position:0% Now,<00:04:00.800><c> I</c><00:04:00.880><c> don't</c><00:04:01.080><c> even</c><00:04:01.280><c> have</c><00:04:01.440><c> to</c><00:04:01.560><c> build</c><00:04:01.880><c> a</c> 00:04:01.910 --> 00:04:01.920 align:start position:0% Now, I don't even have to build a 00:04:01.920 --> 00:04:03.790 align:start position:0% Now, I don't even have to build a dashboard<00:04:02.440><c> myself.</c><00:04:02.960><c> I'm</c><00:04:03.080><c> going</c><00:04:03.200><c> to</c><00:04:03.280><c> ask</c><00:04:03.560><c> Noe</c> 00:04:03.790 --> 00:04:03.800 align:start position:0% dashboard myself. I'm going to ask Noe 00:04:03.800 --> 00:04:06.470 align:start position:0% dashboard myself. I'm going to ask Noe AI<00:04:04.240><c> to</c><00:04:04.360><c> do</c><00:04:04.520><c> it.</c> 00:04:06.470 --> 00:04:06.480 align:start position:0% AI to do it. 00:04:06.480 --> 00:04:08.750 align:start position:0% AI to do it. I<00:04:06.600><c> could</c><00:04:06.840><c> create</c><00:04:07.120><c> it</c><00:04:07.200><c> directly</c><00:04:07.560><c> from</c><00:04:07.760><c> here</c> 00:04:08.750 --> 00:04:08.760 align:start position:0% I could create it directly from here 00:04:08.760 --> 00:04:10.949 align:start position:0% I could create it directly from here using<00:04:08.959><c> the</c><00:04:09.080><c> prompt</c> 00:04:10.949 --> 00:04:10.959 align:start position:0% using the prompt 00:04:10.959 --> 00:04:13.477 align:start position:0% using the prompt or<00:04:11.280><c> you</c><00:04:11.440><c> can</c><00:04:11.600><c> go</c><00:04:11.880><c> to</c><00:04:12.040><c> the</c><00:04:12.200><c> AI</c><00:04:12.760><c> gigantic</c><00:04:13.360><c> agent</c> 00:04:13.477 --> 00:04:13.487 align:start position:0% or you can go to the AI gigantic agent 00:04:13.487 --> 00:04:16.229 align:start position:0% or you can go to the AI gigantic agent [music] 00:04:16.229 --> 00:04:16.239 align:start position:0% 00:04:16.239 --> 00:04:18.150 align:start position:0% and<00:04:16.440><c> build</c><00:04:16.680><c> a</c><00:04:16.760><c> dashboard</c> 00:04:18.150 --> 00:04:18.160 align:start position:0% and build a dashboard 00:04:18.160 --> 00:04:24.350 align:start position:0% and build a dashboard from<00:04:18.400><c> the</c><00:04:18.519><c> chat</c><00:04:18.727><c> [music]</c><00:04:18.840><c> here.</c> 00:04:24.350 --> 00:04:24.360 align:start position:0% 00:04:24.360 --> 00:04:32.030 align:start position:0% I'm<00:04:24.520><c> going</c><00:04:24.640><c> to</c><00:04:24.720><c> keep</c><00:04:24.919><c> my</c><00:04:25.080><c> ask</c><00:04:25.440><c> super</c><00:04:25.760><c> broad.</c> 00:04:32.030 --> 00:04:32.040 align:start position:0% 00:04:32.040 --> 00:04:33.190 align:start position:0% And<00:04:32.160><c> ask</c><00:04:32.400><c> the</c><00:04:32.483><c> [music]</c><00:04:32.520><c> agent</c><00:04:32.840><c> to</c><00:04:32.919><c> build</c><00:04:33.160><c> a</c> 00:04:33.190 --> 00:04:33.200 align:start position:0% And ask the [music] agent to build a 00:04:33.200 --> 00:04:35.270 align:start position:0% And ask the [music] agent to build a dashboard<00:04:33.919><c> showing</c><00:04:34.280><c> me</c><00:04:34.440><c> how</c><00:04:34.640><c> my</c><00:04:34.800><c> store</c><00:04:35.120><c> is</c> 00:04:35.270 --> 00:04:35.280 align:start position:0% dashboard showing me how my store is 00:04:35.280 --> 00:04:45.350 align:start position:0% dashboard showing me how my store is performing. 00:04:45.350 --> 00:04:45.360 align:start position:0% 00:04:45.360 --> 00:04:48.470 align:start position:0% The<00:04:45.480><c> result</c><00:04:46.000><c> is</c><00:04:46.160><c> a</c><00:04:46.200><c> summary</c><00:04:46.680><c> of</c><00:04:46.800><c> my</c><00:04:46.919><c> data</c><00:04:47.200><c> set.</c> 00:04:48.470 --> 00:04:48.480 align:start position:0% The result is a summary of my data set. 00:04:48.480 --> 00:04:50.030 align:start position:0% The result is a summary of my data set. So,<00:04:48.560><c> the</c><00:04:48.680><c> agent</c><00:04:48.960><c> tells</c><00:04:49.200><c> me</c><00:04:49.360><c> that</c><00:04:49.600><c> the</c><00:04:49.720><c> total</c> 00:04:50.030 --> 00:04:50.040 align:start position:0% So, the agent tells me that the total 00:04:50.040 --> 00:04:52.350 align:start position:0% So, the agent tells me that the total revenue<00:04:50.440><c> across</c><00:04:50.720><c> my</c><00:04:50.880><c> stores</c><00:04:51.440><c> averages</c><00:04:52.200><c> just</c> 00:04:52.350 --> 00:04:52.360 align:start position:0% revenue across my stores averages just 00:04:52.360 --> 00:04:54.670 align:start position:0% revenue across my stores averages just over<00:04:52.560><c> $26,000</c><00:04:52.788><c> [music]</c> 00:04:54.670 --> 00:04:54.680 align:start position:0% over $26,000 [music] 00:04:54.680 --> 00:04:57.190 align:start position:0% over $26,000 [music] with<00:04:54.840><c> lots</c><00:04:55.040><c> of</c><00:04:55.120><c> variation</c><00:04:55.840><c> between</c><00:04:56.360><c> 9,000</c><00:04:57.120><c> to</c> 00:04:57.190 --> 00:04:57.200 align:start position:0% with lots of variation between 9,000 to 00:04:57.200 --> 00:04:59.470 align:start position:0% with lots of variation between 9,000 to 53,000. 00:04:59.470 --> 00:04:59.480 align:start position:0% 53,000. 00:04:59.480 --> 00:05:00.870 align:start position:0% 53,000. The<00:04:59.560><c> Snack</c><00:04:59.919><c> Shack,</c><00:04:59.993><c> [music]</c><00:05:00.360><c> which</c><00:05:00.520><c> is</c><00:05:00.640><c> one</c><00:05:00.760><c> of</c> 00:05:00.870 --> 00:05:00.880 align:start position:0% The Snack Shack, [music] which is one of 00:05:00.880 --> 00:05:03.190 align:start position:0% The Snack Shack, [music] which is one of our<00:05:01.000><c> brands,</c><00:05:01.600><c> leads</c><00:05:01.880><c> in</c><00:05:02.000><c> sales</c><00:05:02.680><c> while</c><00:05:02.840><c> Sugar</c> 00:05:03.190 --> 00:05:03.200 align:start position:0% our brands, leads in sales while Sugar 00:05:03.200 --> 00:05:04.830 align:start position:0% our brands, leads in sales while Sugar Bureau<00:05:03.560><c> lags</c> 00:05:04.830 --> 00:05:04.840 align:start position:0% Bureau lags 00:05:04.840 --> 00:05:06.430 align:start position:0% Bureau lags suggesting<00:05:05.233><c> [music]</c><00:05:05.400><c> a</c><00:05:05.440><c> need</c><00:05:05.720><c> to</c><00:05:05.840><c> investigate</c> 00:05:06.430 --> 00:05:06.440 align:start position:0% suggesting [music] a need to investigate 00:05:06.440 --> 00:05:09.150 align:start position:0% suggesting [music] a need to investigate underperformance. 00:05:09.150 --> 00:05:09.160 align:start position:0% underperformance. 00:05:09.160 --> 00:05:10.870 align:start position:0% underperformance. There's<00:05:09.320><c> also</c><00:05:09.760><c> a</c><00:05:09.840><c> section</c><00:05:10.200><c> with</c><00:05:10.320><c> recommended</c> 00:05:10.870 --> 00:05:10.880 align:start position:0% There's also a section with recommended 00:05:10.880 --> 00:05:13.070 align:start position:0% There's also a section with recommended actions.<00:05:11.640><c> Analyze</c><00:05:12.120><c> best-selling</c><00:05:12.640><c> products</c> 00:05:13.070 --> 00:05:13.080 align:start position:0% actions. Analyze best-selling products 00:05:13.080 --> 00:05:14.590 align:start position:0% actions. Analyze best-selling products at<00:05:13.160><c> the</c><00:05:13.240><c> Snack</c><00:05:13.600><c> Shack</c><00:05:14.040><c> to</c><00:05:14.120><c> replicate</c><00:05:14.403><c> [music]</c> 00:05:14.590 --> 00:05:14.600 align:start position:0% at the Snack Shack to replicate [music] 00:05:14.600 --> 00:05:16.990 align:start position:0% at the Snack Shack to replicate [music] success<00:05:15.000><c> in</c><00:05:15.120><c> other</c><00:05:15.360><c> stores,</c><00:05:16.200><c> particularly</c><00:05:16.880><c> at</c> 00:05:16.990 --> 00:05:17.000 align:start position:0% success in other stores, particularly at 00:05:17.000 --> 00:05:18.470 align:start position:0% success in other stores, particularly at Sugar<00:05:17.280><c> Bureau,</c><00:05:17.680><c> which</c><00:05:17.840><c> has</c><00:05:18.000><c> the</c><00:05:18.120><c> lowest</c> 00:05:18.470 --> 00:05:18.480 align:start position:0% Sugar Bureau, which has the lowest 00:05:18.480 --> 00:05:20.470 align:start position:0% Sugar Bureau, which has the lowest sales. 00:05:20.470 --> 00:05:20.480 align:start position:0% sales. 00:05:20.480 --> 00:05:22.350 align:start position:0% sales. Focus<00:05:20.840><c> on</c><00:05:20.960><c> retention</c><00:05:21.480><c> strategies</c><00:05:22.160><c> and</c> 00:05:22.350 --> 00:05:22.360 align:start position:0% Focus on retention strategies and 00:05:22.360 --> 00:05:24.190 align:start position:0% Focus on retention strategies and loyalty<00:05:22.840><c> programs</c><00:05:23.320><c> to</c><00:05:23.440><c> capitalize</c><00:05:24.040><c> on</c><00:05:24.120><c> the</c> 00:05:24.190 --> 00:05:24.200 align:start position:0% loyalty programs to capitalize on the 00:05:24.200 --> 00:05:27.030 align:start position:0% loyalty programs to capitalize on the high<00:05:24.360><c> number</c><00:05:24.760><c> of</c><00:05:24.880><c> repeat</c><00:05:25.240><c> customers.</c><00:05:25.538><c> [music]</c> 00:05:27.030 --> 00:05:27.040 align:start position:0% high number of repeat customers. [music] 00:05:27.040 --> 00:05:30.670 align:start position:0% high number of repeat customers. [music] Let's<00:05:27.240><c> check</c><00:05:27.480><c> out</c><00:05:27.600><c> our</c><00:05:27.720><c> dashboard.</c> 00:05:30.670 --> 00:05:30.680 align:start position:0% 00:05:30.680 --> 00:05:32.510 align:start position:0% The<00:05:30.840><c> data</c><00:05:31.120><c> summary</c><00:05:31.640><c> is</c><00:05:31.800><c> generated</c><00:05:32.320><c> at</c><00:05:32.400><c> the</c> 00:05:32.510 --> 00:05:32.520 align:start position:0% The data summary is generated at the 00:05:32.520 --> 00:05:34.630 align:start position:0% The data summary is generated at the top.<00:05:33.560><c> So,</c><00:05:33.680><c> I'll</c><00:05:33.760><c> expand</c><00:05:34.053><c> [music]</c><00:05:34.200><c> that</c><00:05:34.480><c> so</c><00:05:34.560><c> we</c> 00:05:34.630 --> 00:05:34.640 align:start position:0% top. So, I'll expand [music] that so we 00:05:34.640 --> 00:05:36.670 align:start position:0% top. So, I'll expand [music] that so we can<00:05:34.800><c> see</c><00:05:34.960><c> it</c><00:05:35.040><c> more</c><00:05:35.200><c> clearly.</c> 00:05:36.670 --> 00:05:36.680 align:start position:0% can see it more clearly. 00:05:36.680 --> 00:05:38.310 align:start position:0% can see it more clearly. And<00:05:36.800><c> here</c><00:05:36.919><c> we've</c><00:05:37.080><c> got</c><00:05:37.280><c> total</c><00:05:37.560><c> revenue</c><00:05:38.080><c> over</c> 00:05:38.310 --> 00:05:38.320 align:start position:0% And here we've got total revenue over 00:05:38.320 --> 00:05:42.550 align:start position:0% And here we've got total revenue over time. 00:05:42.550 --> 00:05:42.560 align:start position:0% 00:05:42.560 --> 00:05:46.310 align:start position:0% We<00:05:42.680><c> can</c><00:05:42.919><c> rearrange</c><00:05:43.223><c> [music]</c><00:05:43.440><c> these</c><00:05:43.680><c> widgets</c> 00:05:46.310 --> 00:05:46.320 align:start position:0% We can rearrange [music] these widgets 00:05:46.320 --> 00:05:49.070 align:start position:0% We can rearrange [music] these widgets by<00:05:46.880><c> dragging</c><00:05:47.280><c> and</c><00:05:47.400><c> dropping</c><00:05:47.840><c> them.</c> 00:05:49.070 --> 00:05:49.080 align:start position:0% by dragging and dropping them. 00:05:49.080 --> 00:05:50.710 align:start position:0% by dragging and dropping them. And<00:05:49.200><c> we</c><00:05:49.320><c> can</c><00:05:49.480><c> also</c> 00:05:50.710 --> 00:05:50.720 align:start position:0% And we can also 00:05:50.720 --> 00:05:53.870 align:start position:0% And we can also go<00:05:50.880><c> into</c><00:05:51.120><c> the</c><00:05:51.240><c> tab</c><00:05:52.160><c> to</c><00:05:52.280><c> verify</c> 00:05:53.870 --> 00:05:53.880 align:start position:0% go into the tab to verify 00:05:53.880 --> 00:05:56.190 align:start position:0% go into the tab to verify the<00:05:54.000><c> analysis</c><00:05:54.359><c> [music]</c><00:05:54.800><c> that</c><00:05:55.400><c> the</c><00:05:55.520><c> AI</c><00:05:55.840><c> agent</c> 00:05:56.190 --> 00:05:56.200 align:start position:0% the analysis [music] that the AI agent 00:05:56.200 --> 00:05:57.470 align:start position:0% the analysis [music] that the AI agent used 00:05:57.470 --> 00:05:57.480 align:start position:0% used 00:05:57.480 --> 00:06:09.190 align:start position:0% used and<00:05:57.640><c> to</c><00:05:57.760><c> change</c><00:05:58.160><c> the</c><00:05:58.240><c> visualization</c><00:05:58.960><c> type.</c> 00:06:09.190 --> 00:06:09.200 align:start position:0% 00:06:09.200 --> 00:06:10.730 align:start position:0% Another<00:06:09.520><c> widget</c><00:06:09.800><c> on</c><00:06:09.920><c> the</c><00:06:10.000><c> dashboard</c><00:06:10.720><c> is</c> 00:06:10.730 --> 00:06:10.740 align:start position:0% Another widget on the dashboard is 00:06:10.740 --> 00:06:13.310 align:start position:0% Another widget on the dashboard is [music]<00:06:11.040><c> the</c><00:06:11.240><c> recommendations</c><00:06:12.120><c> widget.</c> 00:06:13.310 --> 00:06:13.320 align:start position:0% [music] the recommendations widget. 00:06:13.320 --> 00:06:14.710 align:start position:0% [music] the recommendations widget. This<00:06:13.520><c> will</c><00:06:13.680><c> generate</c><00:06:14.120><c> findings</c><00:06:14.640><c> with</c> 00:06:14.710 --> 00:06:14.720 align:start position:0% This will generate findings with 00:06:14.720 --> 00:06:16.430 align:start position:0% This will generate findings with recommended<00:06:15.280><c> action</c><00:06:15.600><c> items</c><00:06:16.040><c> for</c><00:06:16.200><c> each</c> 00:06:16.430 --> 00:06:16.440 align:start position:0% recommended action items for each 00:06:16.440 --> 00:06:29.390 align:start position:0% recommended action items for each insight<00:06:17.000><c> that</c><00:06:17.200><c> the</c><00:06:17.320><c> agent</c><00:06:17.640><c> finds.</c> 00:06:29.390 --> 00:06:29.400 align:start position:0% 00:06:29.400 --> 00:06:30.710 align:start position:0% And<00:06:29.520><c> just</c><00:06:29.680><c> like</c><00:06:29.880><c> that,</c><00:06:30.160><c> we're</c><00:06:30.280><c> one</c><00:06:30.480><c> step</c> 00:06:30.710 --> 00:06:30.720 align:start position:0% And just like that, we're one step 00:06:30.720 --> 00:06:32.550 align:start position:0% And just like that, we're one step closer<00:06:31.080><c> to</c><00:06:31.200><c> having</c><00:06:31.600><c> all</c><00:06:31.760><c> of</c><00:06:31.880><c> our</c><00:06:32.040><c> e-commerce</c> 00:06:32.550 --> 00:06:32.560 align:start position:0% closer to having all of our e-commerce 00:06:32.560 --> 00:06:34.990 align:start position:0% closer to having all of our e-commerce metrics<00:06:32.960><c> in</c><00:06:33.080><c> one</c><00:06:33.280><c> place.</c><00:06:34.160><c> No</c><00:06:34.280><c> more</c><00:06:34.480><c> juggling</c><00:06:34.960><c> a</c> 00:06:34.990 --> 00:06:35.000 align:start position:0% metrics in one place. No more juggling a 00:06:35.000 --> 00:06:36.909 align:start position:0% metrics in one place. No more juggling a dozen<00:06:35.320><c> logins</c><00:06:35.840><c> to</c><00:06:35.960><c> see</c><00:06:36.160><c> how</c><00:06:36.280><c> the</c><00:06:36.400><c> business</c><00:06:36.800><c> is</c> 00:06:36.909 --> 00:06:36.919 align:start position:0% dozen logins to see how the business is 00:06:36.919 --> 00:06:39.400 align:start position:0% dozen logins to see how the business is doing.